-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Deprecate indices.merge.scheduler.use_thread_pool setting #129464
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
Deprecate indices.merge.scheduler.use_thread_pool setting #129464
Conversation
|
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
|
Hi @albertzaharovits, I've created a changelog YAML for you. Note that since this PR is labelled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (provided CI passes)
…rrent-merge-scheduler
…rrent-merge-scheduler
…rrent-merge-scheduler
…rrent-merge-scheduler
…rrent-merge-scheduler
…9464) This deprecates the `indices.merge.scheduler.use_thread_pool` setting that was introduced in elastic#120869 because this setting should not normally be used, unless instructed so by engineering to get around temporary issues with the new threadpool-based merge scheduler.
…9464) (#129628) * Deprecate indices.merge.scheduler.use_thread_pool setting (#129464) This deprecates the `indices.merge.scheduler.use_thread_pool` setting that was introduced in #120869 because this setting should not normally be used, unless instructed so by engineering to get around temporary issues with the new threadpool-based merge scheduler. * Update warning msg
…9464) This deprecates the `indices.merge.scheduler.use_thread_pool` setting that was introduced in elastic#120869 because this setting should not normally be used, unless instructed so by engineering to get around temporary issues with the new threadpool-based merge scheduler.
…9464) This deprecates the `indices.merge.scheduler.use_thread_pool` setting that was introduced in elastic#120869 because this setting should not normally be used, unless instructed so by engineering to get around temporary issues with the new threadpool-based merge scheduler.
This deprecates the
indices.merge.scheduler.use_thread_poolsetting that was introduced in #120869 because this setting should not normally be used, unless instructed so by engineering to get around temporary issues with the new threadpool-based merge scheduler.