Message not fully Read while Indexing by ElasticSsearch Client


(mohankumar) #1

Hi ,

We are running elasticsearch production server in 1.5.2 and the client in 1.2.2 for Indexing the data to elasticsearch .I have faced the warnings in the logs as follows,

2016-01-07 10:53:49,985] WARN[Log4jESLogger.java:124] [Dmitri Smerdyakov] Message not fully read (response) for [4] handler org.elasticsearch.action.TransportActionNodeProxy$1@323ba8a, error [false], resetting
[2016-01-07 10:53:50,044] WARN[Log4jESLogger.java:124] [Dmitri Smerdyakov] Message not fully read (response) for [3] handler org.elasticsearch.action.TransportActionNodeProxy$1@1eabbba2, error [false], resetting
[2016-01-07 10:53:51,260] WARN[Log4jESLogger.java:124] [Falcon] Message not fully read (response) for [6] handler org.elasticsearch.action.TransportActionNodeProxy$1@103449d6, error [false], resetting
[2016-01-07 10:53:53,543] WARN[Log4jESLogger.java:124] [Iron Man 2020] Message not fully read (response) for [15] handler org.elasticsearch.action.TransportActionNodeProxy$1@1ded8b25, error [false], resetting

I found this warning because of mismatched client and server versions.IS this cause for data loss or partially loss while indexing.

Thanks & Regards
Moni


(David Pilato) #2

Do you have the same JVM version on both nodes?


(mohankumar) #3

Yes David,We have same version on both client and server with jdk1.8.0_66


(David Pilato) #4

That's strange. 1.x versions are supposed to be compatible (client / node or node / node).

Is there more trace (stack trace) or more details?


(system) #5