You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in this comment, SM should make it easier to set optimal --batch-size for restoring as fast as possible.
In order to achieve that, we should add a special --batch-size=0 value meaning that we want to create batches that result in the fastest restore. This follows the convention used by other flags like --parallel or --rate-limit.
Setting --batch-size=0 would result in sending batches of unlimited amount of sstables, but of size up to 5% of expected node workload.
The text was updated successfully, but these errors were encountered:
This commit allows to set --batch-size=0.
When this happens, batches will be created so that they contain
about 5% of expected node workload during restore.
This allows for creating big, yet evenly distributed batches
without the need to play with the --batch-size flag.
It should also work better fine when backed up cluster
had different amount of nodes than the restore destination
cluster.
Fixes#4059
As described in this comment, SM should make it easier to set optimal --batch-size for restoring as fast as possible.
In order to achieve that, we should add a special
--batch-size=0
value meaning that we want to create batches that result in the fastest restore. This follows the convention used by other flags like--parallel
or--rate-limit
.Setting
--batch-size=0
would result in sending batches of unlimited amount of sstables, but of size up to 5% of expected node workload.The text was updated successfully, but these errors were encountered: