-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Remove exception-mangling in connect/close listeners #127954
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
Open
DaveCTurner
wants to merge
1
commit into
elastic:main
Choose a base branch
from
DaveCTurner:2025/05/09/transport-connect-exception-mangling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Remove exception-mangling in connect/close listeners #127954
DaveCTurner
wants to merge
1
commit into
elastic:main
from
DaveCTurner:2025/05/09/transport-connect-exception-mangling
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The close-listeners are never completed exceptionally today so they do not need the exception mangling of a `ListenableFuture`. The connect- and remove-listeners sometimes see an exception if the connection attempt fails, but they also do not need any exception-mangling. This commit removes the exception-mangling by replacing these `ListenableFuture` instances with `SubscribableListener` ones.
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
Relates #127895 - as implemented today we get all sorts of unnecessary junk in the logs:
With this change we don't do any of that unnecessary wrapping and get something more manageable instead:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Network
Http and internode communication implementations
>non-issue
Team:Distributed Coordination
Meta label for Distributed Coordination team
v9.1.0
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.
The close-listeners are never completed exceptionally today so they do
not need the exception mangling of a
ListenableFuture
. The connect-and remove-listeners sometimes see an exception if the connection
attempt fails, but they also do not need any exception-mangling.
This commit removes the exception-mangling by replacing these
ListenableFuture
instances withSubscribableListener
ones.