-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Update TransportNodesCapabilitiesAction for V9 #122613
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
|
Hi @alexey-ivanov-es, I've created a changelog YAML for you. |
| restApiVersion = RestApiVersion.forMajor(in.readVInt()); | ||
| byte versionFromMessage = (byte) in.readVInt(); | ||
| // V9 can send IMPLICIT_REST_API_VERSION | ||
| restApiVersionMajor = (versionFromMessage != IMPLICIT_REST_API_VERSION) ? versionFromMessage : null; |
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.
8.18/8.19 should be able to understand message sent by v9 node containing either 9 or 0
| out.writeCollection(parameters, StreamOutput::writeString); | ||
| out.writeCollection(capabilities, StreamOutput::writeString); | ||
| out.writeVInt(restApiVersion.major); | ||
| out.writeVInt(restApiVersionMajor); |
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.
8.18/8.19 send only 7 or 8 here, any other node they can form cluster with understands it
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
PR #122609 introduces the ability for a v9 server to send 0 as the REST version in NodeCapabilitiesRequest when it is implicit. This PR ensures that v8.18/v8.19 can correctly read and handle such requests but does not change how v8 nodes send their NodeCapabilitiesRequest. As a result, v8 nodes will still be able to communicate with both v9 and older v8 nodes.