-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Fork Building Aggregate Index Capabilities Response to Management Pool #76333
Fork Building Aggregate Index Capabilities Response to Management Pool #76333
Conversation
It's in the title. It has been observed that the merge step can run for non-trivial amounts of time for very large states so we should fork it to guard the transport threads.
Pinging @elastic/es-distributed (Team:Distributed) |
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, at least it's off the transport worker this way.
Jenkins run elasticsearch-ci/part-1 |
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.
LGTM2
Thanks David & Henning :) |
elastic#76333) It's in the title. It has been observed that the merge step can run for non-trivial amounts of time for very large states so we should fork it to guard the transport threads.
elastic#76333) It's in the title. It has been observed that the merge step can run for non-trivial amounts of time for very large states so we should fork it to guard the transport threads.
Pinging @elastic/es-search (Team:Search) |
It's in the title. It has been observed that the merge step can run for
non-trivial amounts of time for very large states so we should fork
it to guard the transport threads.