From: Wido den Hollander <wido@42on.com>
To: Gregory Farnum <greg@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: 5GB object limit in the RADOS Gateway
Date: Thu, 30 May 2013 19:50:49 +0200 [thread overview]
Message-ID: <51A79179.9080501@42on.com> (raw)
In-Reply-To: <CAPYLRzgFTgv3pPUdLny3MdiZCpFPCfSY-aj5+3sf16jBtL7T-Q@mail.gmail.com>
On 05/30/2013 07:47 PM, Gregory Farnum wrote:
> On Thu, May 30, 2013 at 10:42 AM, Wido den Hollander <wido@42on.com> wrote:
>> Hi,
>>
>> I was checking the source code today and found this macro:
>>
>> #define RGW_MAX_PUT_SIZE (5ULL*1024*1024*1024)
>>
>> Why is that limit in place? Was that to mimic Amazon S3? (Which is at 5T
>> now).
>>
>> I know that object size limit something that should be there, but just
>> trying to find the reasoning behind this limit.
>>
>> Couldn't we make this configurable at least?
>
> That's the limit on an individual HTTP PUT operation. You can make
> larger objects, but they need to be placed with multi-part uploads.
> (I'm not sure what the actual limit is, if there is one.)
> -Greg
Heh? My client gave me an error today and I thought that was really
doing multipart uploads.
Checking again I see that s3cmd doesn't do multipart. That confused me
So it doesn't seem there is an object size limitation after all, so you
can store object as large as you like.
> Software Engineer #42 @ http://inktank.com | http://ceph.com
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
prev parent reply other threads:[~2013-05-30 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 17:42 5GB object limit in the RADOS Gateway Wido den Hollander
2013-05-30 17:47 ` Gregory Farnum
2013-05-30 17:50 ` Wido den Hollander [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A79179.9080501@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.