-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Labels
>bug
:Core/Infra/Node Lifecycle
Node startup, bootstrapping, and shutdown
Team:Core/Infra
Meta label for core/infra team
Comments
DaveCTurner
added
>bug
:Core/Infra/Node Lifecycle
Node startup, bootstrapping, and shutdown
labels
Apr 24, 2024
Pinging @elastic/es-core-infra (Team:Core/Infra) |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Apr 24, 2024
the same bug applies to |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
May 8, 2024
Removes the default constructors for `MasterRequest`, `MasterReadRequest` and `AcknowledgedRequest` in favour of constructors which require subclasses to specify the relevant timeouts. This will avoid bugs like elastic#107857 which are caused by a missing `super()` call. Also deprecates and renames the default to make it clear it should not be used in new code. Relates elastic#107984
elasticsearchmachine
pushed a commit
that referenced
this issue
May 13, 2024
Removes the default constructors for `MasterRequest`, `MasterReadRequest` and `AcknowledgedRequest` in favour of constructors which require subclasses to specify the relevant timeouts. This will avoid bugs like #107857 which are caused by a missing `super()` call. Also deprecates and renames the default to make it clear it should not be used in new code. Relates #107984
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
PutShutdownNodeAction.Request
is anAcknowledgedRequest
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 superclasswriteTo()
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.The text was updated successfully, but these errors were encountered: