Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Bandwidth Throttling for S3 Transfer Manager #1103

Closed
millems opened this issue Apr 5, 2017 · 3 comments
Closed

Feature Request: Bandwidth Throttling for S3 Transfer Manager #1103

millems opened this issue Apr 5, 2017 · 3 comments
Assignees
Labels
feature-request A feature should be added or improved.

Comments

@millems
Copy link
Contributor

millems commented Apr 5, 2017

The S3 transfer manager should be able to limit (in some way) the bandwidth used when uploading multiple files to prevent saturating the network on a host. This is similar to the feature discussed in this blog post: https://www.instaclustr.com/blog/2016/04/20/cassandra-backups-using-aws-transfermanager/

@millems millems added the feature-request A feature should be added or improved. label Apr 5, 2017
@arunagrawal84
Copy link

+1
I am making some changes to Netflix/Priam for backups and was bummed to find that this is not a standard feature yet. It makes sense as S3 is used for backups and while doing a backup you don't want to throttle the bandwidth of the instance.

@johnbonds
Copy link

+1
Using Amazon S3 to do database backups. When transferring the backup to S3, it uses up all available bandwidth. I also use Galera so the combination of the 2 causes actual SQL errors on my other nodes.

@millems
Copy link
Contributor Author

millems commented Mar 31, 2020

We do not currently intend to implement this in V1 of the Java SDK. Keep an eye out on aws/aws-sdk-java-v2#37 for this functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants