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

Throttling of recovery (both gateway recovery and peer node recovery) #176

Closed
kimchy opened this issue May 16, 2010 · 1 comment
Closed

Comments

@kimchy
Copy link
Member

kimchy commented May 16, 2010

There are two recoveries going on with elasticsearch. The first is when the first even primary is created, and is then recovery from the gateway, and the second is when a shard gets created / relocated into a another node.

This can be a taxing operation on the machine, especially when several shards are recovering at the same time. For this, we have two new settings that allow to throttle it:

indices.recovery.throttler.concurrent_recoveries: The number of concurrent recoveries allowed at the same time on a node. Defaults to the number of cores.

indices.recovery.throttler.concurrent_streams: The number of concurrent streams transfers allowed during recovery. A stream basically maps to an Lucene index file, which is a file that exists within specific shard index. Defaults to the number of cores.

@kimchy
Copy link
Member Author

kimchy commented May 16, 2010

Throttling of recovery (both gateway recovery and peer node recovery), closed by 216dda3.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant