# Message not fully Read while Indexing by ElasticSsearch Client

**URL:** <https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602>\
**Category:** Elasticsearch\
**Created:** [January 7, 2016, 11:06am UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602 "2016-01-07T11:06:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![moni15moni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moni15moni/32/42311_2.png) [@moni15moni](https://discuss.elastic.co/u/moni15moni)\
**Post date:** [January 7, 2016, 11:06am UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602/1 "2016-01-07T11:06:45Z")

</div>

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](http://versions.IS) this cause for data loss or partially loss while indexing.

Thanks & Regards  
Moni

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 7, 2016, 12:44pm UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602/2 "2016-01-07T12:44:27Z")

</div>

Do you have the same JVM version on both nodes?

---

<div class="post-metadata">

**Author:** ![moni15moni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moni15moni/32/42311_2.png) [@moni15moni](https://discuss.elastic.co/u/moni15moni)\
**Post date:** [January 8, 2016, 8:49am UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602/3 "2016-01-08T08:49:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 8, 2016, 9:06am UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602/4 "2016-01-08T09:06:49Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:26pm UTC](https://discuss.elastic.co/t/message-not-fully-read-while-indexing-by-elasticssearch-client/38602/5 "2017-07-05T23:26:06Z")

</div>