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
Is your feature request related to a problem? Please describe
We currently have a constant DEFAULT_CHUNK_SIZE (value is 512 KB) recovery setting which can not be modified dynamically . We will need to increase the recovery chunk size while non-remote to remote-store migration is happening. During translog recovery phase of migration, a chunk of translog operations are sent from non-remote node to remote node, and on receiving each chunk the shard gets synced, resulting in a new translog generation. Inorder to control large number of translog files getting generated, we will increase the chunk_size.
Describe the solution you'd like
Add recovery chunk size as dynamic cluster setting.
Related component
Storage:Remote
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
We currently have a constant
DEFAULT_CHUNK_SIZE
(value is 512 KB) recovery setting which can not be modified dynamically . We will need to increase the recovery chunk size while non-remote to remote-store migration is happening. During translog recovery phase of migration, a chunk of translog operations are sent from non-remote node to remote node, and on receiving each chunk the shard gets synced, resulting in a new translog generation. Inorder to control large number of translog files getting generated, we will increase thechunk_size
.Describe the solution you'd like
Add recovery chunk size as dynamic cluster setting.
Related component
Storage:Remote
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: