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

PutShutdownNodeAction.Request does not preserve parent task or timeouts on the wire #107857

Closed
DaveCTurner opened this issue Apr 24, 2024 · 2 comments · Fixed by #107862
Closed
Labels
>bug :Core/Infra/Node Lifecycle Node startup, bootstrapping, and shutdown Team:Core/Infra Meta label for core/infra team

Comments

@DaveCTurner
Copy link
Contributor

PutShutdownNodeAction.Request is an AcknowledgedRequest whose transport-protocol representation therefore should start with the parent task ID followed by the ?masterNodeTimeout and ?timeout parameters. However we do not call the superclass writeTo() method when serializing it so these fields are omitted, and therefore we end up with the default 30s timeouts (and no parent task ID) on a remote master node.

@DaveCTurner DaveCTurner added >bug :Core/Infra/Node Lifecycle Node startup, bootstrapping, and shutdown labels Apr 24, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Apr 24, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@DaveCTurner
Copy link
Contributor Author

the same bug applies to DeleteShutdownNodeAction.Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Core/Infra/Node Lifecycle Node startup, bootstrapping, and shutdown Team:Core/Infra Meta label for core/infra team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants