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

[8.x] Add deprecation warning to TransportHandshaker (#123188) #123627

Merged
merged 7 commits into from
Mar 4, 2025

Conversation

JVerwolf
Copy link
Contributor

Backports the following commits to 8.x:

This PR adds a deprecation warning log to the TransportHandshaker when connecting with nodes < v8.18.
@JVerwolf JVerwolf added :Core/Infra/Core Core issues without another label >deprecation auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Core/Infra Meta label for core/infra team labels Feb 27, 2025
@DaveCTurner DaveCTurner removed the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Feb 27, 2025
@DaveCTurner
Copy link
Contributor

I think the situation in 8.19 is a little different - after upgrading to 8.19 you can't go to 9.0, only 9.1, and 9.1 will reject connections from 8.18-and-earlier. I've removed the auto-merge label here while we address that.

will not be supported from version 9.1.0 onwards. You must upgrade all your clusters to version 8.19.0 or later
before upgrading any of your clusters to 9.1.0 or later.
impact: >
Upgrade all of your clusters to at least 8.19.0 before upgrading any of them to 9.1.0 or later.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I updated the release notes to reference 8.19 and 9.1

@@ -171,6 +176,7 @@ final class TransportHandshaker {
);

static final String HANDSHAKE_ACTION_NAME = "internal:tcp/handshake";
static final TransportVersion V8_19_FIRST_VERSION = TransportVersions.INITIAL_ELASTICSEARCH_8_19;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Double checking, Is this the first TV on 8.19?

) {
return Strings.format(
"Performed a handshake with a remote node with version [%s/%s] received on [%s] which "
+ "will be incompatible after this node on version [%s/%s] is upgraded to >= 9.1.",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I changed this from 9.x. to >= 9.1.

@JVerwolf JVerwolf requested review from a team, rjernst and DaveCTurner February 27, 2025 22:28
Copy link
Member

@rjernst rjernst left a comment

Choose a reason for hiding this comment

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

LGTM

communication within a cluster and communication across clusters (e.g. for <<modules-cross-cluster-search,{ccs}>> or
<<xpack-ccr,{ccr}>>).

{es} will report in its <<deprecation-logging, deprecation logging>> each time it opens a connection to a node that
Copy link
Member

Choose a reason for hiding this comment

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

nit: deprecation logging -> deprecation log

@JVerwolf JVerwolf merged commit 6ff283a into elastic:8.x Mar 4, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Core/Infra/Core Core issues without another label >deprecation Team:Core/Infra Meta label for core/infra team v8.19.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants