Skip to content

transport: log network reconnects with same peer process #129439

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

schase-es
Copy link
Contributor

Backports the following commit for ES-11448 to 8.19:

  • transport: log network reconnects with same peer process PR 128415

NodeConnectionsService now caches the ephemeralId (created on process-start) of
peer nodes on network disconnect on the node's ConnectionTarget object.  On
reconnect, when a peer has the same ephemeralId as it did in the previous
connection, this is logged to indicate a network failure instead of a restart.

Closes ES-11448
@schase-es schase-es requested a review from nicktindall June 13, 2025 19:10
@schase-es schase-es added >non-issue :Distributed Coordination/Network Http and internode communication implementations backport v8.19.0 labels Jun 13, 2025
The doc pages for 8.19 turn out to use a different URL base, with
elastic.co/guide instead of elastic.co/docs. This tripped up the troubleshooting
page reference in the log matcher.
@schase-es
Copy link
Contributor Author

The doc page URLs turn out to have a different format in 8.19. I issued a small change in the test pattern matcher to fix it.

Copy link
Contributor

@nicktindall nicktindall left a comment

Choose a reason for hiding this comment

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

LGTM

@schase-es schase-es merged commit 5ff538b into elastic:8.19 Jun 16, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Distributed Coordination/Network Http and internode communication implementations >non-issue v8.19.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants