Core: dynamic updates to max_merge_count is ignored by index throttling #8132
Assignees
Labels
Comments
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…he next merge start/finish Previously such changes were never noticed, and index throttling kept kicking in at the original setting from startup. Closes elastic#8136 Closes elastic#8132
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…he next merge start/finish Previously such changes were never noticed, and index throttling kept kicking in at the original setting from startup. Closes elastic#8136 Closes elastic#8132
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With #6066 we added index throttling when merges cannot keep up, which is important since this ensures index remains healthy (does not develop ridiculous number of segments).
It works by watching the number of merges that need to run, and if this exceeds max_merge_count, it starts throttling.
However, max_merge_count is dynamically updatable, but when you update it dynamically, the index throttling doesn't notice and keeps throttling at the original max_merge_count (on ES startup).
The text was updated successfully, but these errors were encountered: