Make RGW_MAX_PUT_SIZE configurable
/src/rgw/rgw_common.h has a #define for RGW_MAX_PUT_SIZE which limits uploads to 5GB. Please consider this for a configurable option.
rgw: Make RGW_MAX_PUT_SIZE configurable
The 5GB limit of a single operation uploading was part of S3 spec.
However some private setups may have some special requirements
on this limit. It's more convinent to have a configurable value.
Signed-off-by: Yuan Zhou <firstname.lastname@example.org>
This is a part of the S3 spec, and anybody using larger objects should probably be using multi-part upload. It's obviously not hard to change, but do we have any credible use cases for making it larger?
A customer requests that we consider making this parameter larger. A configurable parameter might be a good compromise.
I will find out what the reasoning for large uploads are vs. multi-part.
- Status changed from New to Resolved
This was implemented a while back, using the rgw_max_put_size configurable.
- Copied to Backport #14569: hammer: Make RGW_MAX_PUT_SIZE configurable added
- Status changed from Resolved to Pending Backport
- Backport set to hammer
- Status changed from Pending Backport to Resolved
Also available in: Atom