Project

General

Profile

Feature #6999

Make RGW_MAX_PUT_SIZE configurable

Added by Brian Andrus almost 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12/13/2013
Due date:
% 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.


Related issues

Copied to rgw - Backport #14569: hammer: Make RGW_MAX_PUT_SIZE configurable Resolved

Associated revisions

Revision 4aa102f9 (diff)
Added by Yuan Zhou over 3 years ago

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.

Fixes: #6999

Signed-off-by: Yuan Zhou <>

History

#1 Updated by Greg Farnum almost 5 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?

#2 Updated by Brian Andrus almost 5 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.

#3 Updated by Yehuda Sadeh about 3 years ago

  • Status changed from New to Resolved

This was implemented a while back, using the rgw_max_put_size configurable.

#4 Updated by Nathan Cutler almost 3 years ago

  • Copied to Backport #14569: hammer: Make RGW_MAX_PUT_SIZE configurable added

#5 Updated by Nathan Cutler almost 3 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to hammer

#6 Updated by Loic Dachary almost 3 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF