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

Lot's of warn logs related to FreeContext #6147

Closed
s1monw opened this issue May 13, 2014 · 0 comments · Fixed by #6148
Closed

Lot's of warn logs related to FreeContext #6147

s1monw opened this issue May 13, 2014 · 0 comments · Fixed by #6148

Comments

@s1monw
Copy link
Contributor

s1monw commented May 13, 2014

I see tons of these logs when I run some tests:

[2014-05-13 12:17:52,428][WARN ][org.elasticsearch.transport.netty] [node_1] Message not fully read (response) for [91] handler org.elasticsearch.transport.EmptyTransportResponseHandler@7bfccc86, error [false], resetting
[2014-05-13 12:17:52,432][WARN ][org.elasticsearch.transport.netty] [node_2] Message not fully read (response) for [50] handler org.elasticsearch.transport.EmptyTransportResponseHandler@7bfccc86, error [false], resetting
...

I think this is related to #5730 since we now actually send a non-empty response back on freeContext.

s1monw added a commit to s1monw/elasticsearch that referenced this issue May 13, 2014
Since elastic#5730 we write a boolean in the FreeContextResponse which should be deserialized

Closes elastic#6147
s1monw added a commit that referenced this issue May 13, 2014
Since #5730 we write a boolean in the FreeContextResponse which should be deserialized

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

Successfully merging a pull request may close this issue.

1 participant