feat: CLI add rate limit logic to gaia dump and restore #1607
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.
Description
Added some sleep logic in the CLI to wait between batches for
gaia_dump_bucket
andgaia_restore_bucket
as some users have been hitting the rate limit when dumping their Gaia bucket as they have many files (> 200).I did manually test the logic and with the current config not hitting the rate limit, uploading 99 files every mins does hit the rate limit so switched to 99 every 2 mins to get it to work.
Breaking change?
No
Example
Create a bucket with many files and see that you can download/upload all of them without hitting the rate limit.
Checklist