Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support task cancellation cross clusters #55779
Support task cancellation cross clusters #55779
Changes from 1 commit
b1f93d8
85081f5
617bc35
5316931
12264b7
8ed7ed0
5349d86
340b43e
7bc74a7
ba5c6ac
b46cbe3
f66238f
62274db
3dc38e7
bec72b8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
In case of "proxy mode" connections (see also
ProxyConnectionStrategy
),targetNode.getVersion()
will always returnVersion.CURRENT.minimumCompatibilityVersion()
AFAICS, which means that this request won't be send to those nodes.The actual version of the node on the other side is available using
channel.getVersion()
.On the other hand
channel.getNode
will return the (possibly fake)DiscoveryNode
object that was used to create the connection./cc: @tbrooks8 This is quite trappy, anything we can change in the transport in the short term to avoid this?
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.
I've modified the handshaking to update the version of the target node with its actual version. I also exposed the proxy node so that we can check the version of the proxy node. I think we are good here.