Skip to content
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 response reading in TransportNodesAction #97899

Conversation

DaveCTurner
Copy link
Contributor

All TransportNodesAction implementations fork before computing the final
response, but in some cases (notably TransportNodesStatsAction) even reading
the node-level responses is too expensive to run on a transport_worker
thread. With this commit we fork the deserialization of the node-level
responses to the final executor too.

All `TransportNodesAction` implementations fork before computing the final
response, but in some cases (notably `TransportNodesStatsAction`) even reading
the node-level responses is too expensive to run on a `transport_worker`
thread. With this commit we fork the deserialization of the node-level
responses to the final executor too.
@DaveCTurner DaveCTurner added >bug :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. v8.10.0 labels Jul 24, 2023
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Meta label for distributed team label Jul 24, 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)

@DaveCTurner DaveCTurner merged commit 2d9ea80 into elastic:main Jul 24, 2023
12 checks passed
@DaveCTurner DaveCTurner deleted the 2023/07/24/fork-nodes-action-response-reading branch July 24, 2023 14:57
felixbarny pushed a commit to felixbarny/elasticsearch that referenced this pull request Aug 3, 2023
All `TransportNodesAction` implementations fork before computing the final
response, but in some cases (notably `TransportNodesStatsAction`) even reading
the node-level responses is too expensive to run on a `transport_worker`
thread. With this commit we fork the deserialization of the node-level
responses to the final executor too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. Team:Distributed Meta label for distributed team v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants