backup_restore_batch_size_for_keeper_multi
Maximum size of batch for multi request to [Zoo]Keeper during backup or restorebackup_restore_batch_size_for_keeper_multiread
Maximum size of batch for multiread request to [Zoo]Keeper during backup or restorebackup_restore_failure_after_host_disconnected_for_seconds
If a host during a BACKUP ON CLUSTER or RESTORE ON CLUSTER operation doesn’t recreate its ephemeral ‘alive’ node in ZooKeeper for this amount of time then the whole backup or restore is considered as failed. This value should be bigger than any reasonable time for a host to reconnect to ZooKeeper after a failure. Zero means unlimited.backup_restore_finish_timeout_after_error_sec
How long the initiator should wait for other host to react to the ‘error’ node and stop their work on the current BACKUP ON CLUSTER or RESTORE ON CLUSTER operation.backup_restore_keeper_fault_injection_probability
Approximate probability of failure for a keeper request during backup or restore. Valid value is in interval [0.0f, 1.0f]backup_restore_keeper_fault_injection_seed
0 - random seed, otherwise the setting valuebackup_restore_keeper_max_retries
Max retries for [Zoo]Keeper operations in the middle of a BACKUP or RESTORE operation. Should be big enough so the whole operation won’t fail because of a temporary [Zoo]Keeper failure.backup_restore_keeper_max_retries_while_handling_error
Max retries for [Zoo]Keeper operations while handling an error of a BACKUP ON CLUSTER or RESTORE ON CLUSTER operation.backup_restore_keeper_max_retries_while_initializing
Max retries for [Zoo]Keeper operations during the initialization of a BACKUP ON CLUSTER or RESTORE ON CLUSTER operation.backup_restore_keeper_retry_initial_backoff_ms
Initial backoff timeout for [Zoo]Keeper operations during backup or restorebackup_restore_keeper_retry_max_backoff_ms
Max backoff timeout for [Zoo]Keeper operations during backup or restore Cloud default value:60000.
backup_restore_keeper_value_max_size
Maximum size of data of a [Zoo]Keeper’s node during backupbackup_restore_s3_retry_attempts
Setting for Aws::Client::RetryStrategy, Aws::Client does retries itself, 0 means no retries. It takes place only for backup/restore.backup_restore_s3_retry_initial_backoff_ms
Initial backoff delay in milliseconds before the first retry attempt during backup and restore. Each subsequent retry increases the delay exponentially, up to the maximum specified bybackup_restore_s3_retry_max_backoff_ms
backup_restore_s3_retry_jitter_factor
Jitter factor applied to the retry backoff delay in Aws::Client::RetryStrategy during backup and restore operations. The computed backoff delay is multiplied by a random factor in the range [1.0, 1.0 + jitter], up to the maximumbackup_restore_s3_retry_max_backoff_ms. Must be in [0.0, 1.0] interval