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

Netty request/response tracer should wait for send #18500

Merged
merged 1 commit into from
May 20, 2016
Merged

Netty request/response tracer should wait for send #18500

merged 1 commit into from
May 20, 2016

Conversation

jasontedor
Copy link
Member

We write to Netty channels in an async fashion, but notify listeners via
a transport service adapter before we are certain that the channel write
succeeded. In particular, the tracer logs are implemented via a
transport service adapter and this means that we can write tracer logs
before a write was successful and in some cases the write might fail
leading to misleading logs. This commit attaches the transport service
adapters to channel writes as a listener so that the notification occurs
only after a successful write.

We write to Netty channels in an async fashion, but notify listeners via
a transport service adapter before we are certain that the channel write
succeeded. In particular, the tracer logs are implemented via a
transport service adapter and this means that we can write tracer logs
before a write was successful and in some cases the write might fail
leading to misleading logs. This commit attaches the transport service
adapters to channel writes as a listener so that the notification occurs
only after a successful write.
@jaymode
Copy link
Member

jaymode commented May 20, 2016

LGTM

@jasontedor jasontedor removed the review label May 20, 2016
@jasontedor jasontedor merged commit 4c7993e into elastic:master May 20, 2016
@jasontedor jasontedor deleted the async-transport-service-adapter branch May 20, 2016 20:26
jasontedor added a commit that referenced this pull request May 24, 2016
This commit backports commit 4c7993e
from master to 2.x.

Relates #18500
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants