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

Remove 8.11 node version inference code #116019

Merged
merged 6 commits into from
Nov 7, 2024

Conversation

thecoop
Copy link
Member

@thecoop thecoop commented Oct 31, 2024

Remove the mapping from version to transport version needed to communicate with pre-8.11 nodes. This is needed to remove Version from DiscoveryNode entirely (see #115434)

@thecoop thecoop added :Core/Infra/Core Core issues without another label >refactoring labels Oct 31, 2024
@thecoop thecoop requested a review from edsavage October 31, 2024 14:16
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team v9.0.0 labels Oct 31, 2024
@elasticsearchmachine
Copy link
Collaborator

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

@thecoop
Copy link
Member Author

thecoop commented Oct 31, 2024

@edsavage am I correct in thinking that 8.18+ nodes will always have ML and Transform config version attributes on them?

@thecoop
Copy link
Member Author

thecoop commented Oct 31, 2024

@elasticmachine update branch

@thecoop thecoop requested a review from a team October 31, 2024 17:08
@thecoop
Copy link
Member Author

thecoop commented Nov 6, 2024

@elasticmachine update branch

@edsavage
Copy link
Contributor

edsavage commented Nov 6, 2024

@edsavage am I correct in thinking that 8.18+ nodes will always have ML and Transform config version attributes on them?

Yes, that's correct.

Copy link
Contributor

@ldematte ldematte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
One question: this PR assumes that v9 nodes will never talk to "old" v8 nodes, but just with v8.last.
My understanding is that this is what we want to do, but do we have a barrier in place? Is it enforced somewhere e.g. in JoinRequest?
(it's just curiosity on my side)

if (transformConfigVerStr != null) {
return fromString(transformConfigVerStr);
}
return fromId(node.getPre811VersionId().orElseThrow(() -> new IllegalStateException("getting legacy version id not possible")));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: this is the last usage of getPre811VersionId, can we remove it? Or do you want to do that in another PR?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm removing it in #115434

@thecoop
Copy link
Member Author

thecoop commented Nov 7, 2024

Yes, v9 will only be able to talk to 8.18. This is enforced by TransportVersions.MINIMUM_COMPATIBLE, which we won't be able to set until we know what the transport version for 8.18 is.

@thecoop
Copy link
Member Author

thecoop commented Nov 7, 2024

@elasticmachine rerun elasticsearch-ci/part-2

@thecoop thecoop merged commit 908d34d into elastic:main Nov 7, 2024
16 checks passed
@thecoop thecoop deleted the remove-811-version-mapping branch November 7, 2024 12:03
kderusso pushed a commit to kderusso/elasticsearch that referenced this pull request Nov 7, 2024
alexey-ivanov-es pushed a commit to alexey-ivanov-es/elasticsearch that referenced this pull request Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >refactoring Team:Core/Infra Meta label for core/infra team v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants