Skip to content

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

Conversation

DaveCTurner
Copy link
Contributor

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 #97914

`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
@DaveCTurner DaveCTurner added >bug :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. v8.10.0 labels Jul 25, 2023
@elasticsearchmachine
Copy link
Collaborator

Hi @DaveCTurner, I've created a changelog YAML for you.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@elasticsearchmachine elasticsearchmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Jul 25, 2023
@DaveCTurner
Copy link
Contributor Author

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.

DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 27, 2023
`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
Copy link
Contributor

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@DaveCTurner DaveCTurner added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Jul 27, 2023
Copy link
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM2

@elasticsearchmachine elasticsearchmachine merged commit 3a2a1c2 into elastic:main Jul 27, 2023
@DaveCTurner DaveCTurner deleted the 2023/07/25/TransportBroadcastByNodeAction-forking branch July 27, 2023 11:19
DaveCTurner added a commit that referenced this pull request Jul 27, 2023
`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
@DaveCTurner DaveCTurner restored the 2023/07/25/TransportBroadcastByNodeAction-forking branch June 17, 2024 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >bug :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TransportBroadcastByNodeAction does O(#shards) work on transport worker thread
4 participants