s3.buckets : allow spreading chunks across buckets #1625
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thorfour
force-pushed
the
multi-s3
branch
2 times, most recently
from
6dac32f
to
1128fc3
Compare
blockloop
reviewed
Aug 28, 2019
bboreham
approved these changes
Sep 12, 2019
thorfour
force-pushed
the
multi-s3
branch
2 times, most recently
from
ccc6c0e
to
6b03b0f
Compare
khaines
approved these changes
Sep 12, 2019
Signed-off-by: Thor <thansen@digitalocean.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
s3 buckets have per bucket API limits, to circumvent hitting API limits we can spread chunks across buckets.
This PR introduces a new flag
s3.bucketsthat takes a comma separated list of bucket names to spread chunks across.