Actions
Feature #6999
closedMake RGW_MAX_PUT_SIZE configurable
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Support
Tags:
Backport:
hammer
Reviewed:
Affected Versions:
Pull request ID:
Description
/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.
Updated by Greg Farnum over 10 years ago
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?
Updated by Brian Andrus over 10 years ago
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.
Updated by Yehuda Sadeh over 8 years ago
- Status changed from New to Resolved
This was implemented a while back, using the rgw_max_put_size configurable.
Updated by Nathan Cutler over 8 years ago
- Copied to Backport #14569: hammer: Make RGW_MAX_PUT_SIZE configurable added
Updated by Nathan Cutler over 8 years ago
- Status changed from Resolved to Pending Backport
- Backport set to hammer
Updated by Loïc Dachary about 8 years ago
- Status changed from Pending Backport to Resolved
Actions