Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

This is related to #27422. Right now when we do a write in the netty
transport, we attach a listener to the future. When you submit a write
on the netty event loop and the event loop is shutdown, the onFailure
method is called. Unfortunately, netty then tries to notify the listener
which cannot be done without dispatching to the event loop. In this
case, the dispatch fails and netty logs and error and does not tell us.

This commit checks that netty is still running before sending a message.
This will not 100% fix this issue, but it should reduce it.

This is related to elastic#27422. Right now when we do a write in the netty
transport, we attach a listener to the future. When you submit a write
on the netty event loop and the event loop is shutdown, the onFailure
method is called. Unfortunately, netty then tries to notify the listener
which cannot be done without dispatching to the event loop. In this
case, the dispatch fails and netty logs and error and does not tell us.

This commit checks that netty is still running before sending a message.
This will not 100% fix this issue, but it should reduce it.
@Tim-Brooks
Copy link
Contributor Author

This is a backport of #27459 to 5.6.

Copy link
Member

@jaymode jaymode left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

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

LGTM, let's give it a try.

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 v5.6.7

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants