-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Avoid transport_worker thread in TransportBroadcastByNodeAction #97920
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
Avoid transport_worker thread in TransportBroadcastByNodeAction #97920
Conversation
`TransportBroadcastByNodeAction` derivatives do work which scales as the number of shards in the cluster, both during coordination and when processing responses. We must therefore not do this work on `transport_worker` threads. Closes elastic#97914
Hi @DaveCTurner, I've created a changelog YAML for you. |
Pinging @elastic/es-distributed (Team:Distributed) |
Failures are apparently because we don't fork when handling responses from remote clusters, and we retrieve indices stats from the remote cluster in CCR. I opened #97922 to address that first. |
`TransportBroadcastAction` derivatives do work which scales as the number of shards in the cluster, both during coordination and when processing responses. We must therefore not do this work on `transport_worker` threads. Relates elastic#97920
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
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
`TransportBroadcastAction` derivatives do work which scales as the number of shards in the cluster, both during coordination and when processing responses. We must therefore not do this work on `transport_worker` threads. Relates #97920
TransportBroadcastByNodeAction
derivatives do work which scales as thenumber of shards in the cluster, both during coordination and when
processing responses. We must therefore not do this work on
transport_worker
threads.Closes #97914