We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Read full message on free context
d8c02c2
Since elastic#5730 we write a boolean in the FreeContextResponse which should be deserialized Closes elastic#6147
b9e7533
Since #5730 we write a boolean in the FreeContextResponse which should be deserialized Closes #6147
Successfully merging a pull request may close this issue.
I see tons of these logs when I run some tests:
I think this is related to #5730 since we now actually send a non-empty response back on freeContext.
The text was updated successfully, but these errors were encountered: