# EOFException during discovery **URL:** \ **Category:** Elasticsearch\ **Created:** [January 9, 2012, 2:14pm UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325 "2012-01-09T14:14:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Wojciech\_Durczynski](https://avatars.discourse-cdn.com/v4/letter/w/fbc32d/32.png) [@Wojciech\_Durczynski](https://discuss.elastic.co/u/Wojciech_Durczynski)\ **Post date:** [January 9, 2012, 2:14pm UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325/1 "2012-01-09T14:14:41Z")
Hello I have two ES clusters (different cluster names) in my network. Nodes discovery is via multicast, Both clusters was version 0.17.8 but I upgraded one of them to use ES 0.18.6. And now upgraded cluster nodes log this exception very often (log files grow very fast): 16:28:57,744 WARN [cast#receiver-pool-16-thread-1] asticsearch.discovery.zen.ping.multicast [,,,] - [Madame Menace] failed to read requesting node from /10.133.105.131:54328 java.io.EOFException at org.elasticsearch.common.io.stream.BytesStreamInput.readByte(BytesStreamInput.java:92) at org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:80) at org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:74) at org.elasticsearch.Version.readVersion(Version.java:55) at org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:221) at org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:207) at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:364) at java.lang.Thread.run(Thread.java:619) Of course disabling or upgrading second cluster solves problem but why is it impossible to maintain two clusters with different versions and cluster names? How to disable this warning in logging configuration? Regards Wojciech Durczyński ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 9, 2012, 2:22pm UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325/2 "2012-01-09T14:22:25Z")
It is possible to maintain two different versions, its just the exception that is annoying, it might make sense to change the log level on this one... . 2012/1/9 Wojciech Durczyński [wojciech.durczynski@comarch.com](mailto:wojciech.durczynski@comarch.com) > Hello > > I have two ES clusters (different cluster names) in my network. Nodes > discovery is via multicast, > Both clusters was version 0.17.8 but I upgraded one of them to use ES > 0.18.6. > And now upgraded cluster nodes log this exception very often (log files > grow very fast): > > 16:28:57,744 WARN [cast#receiver-pool-16-thread-1] > asticsearch.discovery.zen.ping.multicast [,,,] - [Madame Menace] failed to > read requesting node from /10.133.105.131:54328 > java.io.EOFException > at > org.elasticsearch.common.io.stream.BytesStreamInput.readByte(BytesStreamInput.java:92) > at > org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:80) > at > org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:74) > at org.elasticsearch.Version.readVersion(Version.java:55) > at > org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:221) > at > org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:207) > at > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:364) > at java.lang.Thread.run(Thread.java:619) > > Of course disabling or upgrading second cluster solves problem but why is > it impossible to maintain two clusters with different versions and cluster > names? > How to disable this warning in logging configuration? > > Regards > Wojciech Durczyński ---
**Author:** ![Wojciech\_Durczynski](https://avatars.discourse-cdn.com/v4/letter/w/fbc32d/32.png) [@Wojciech\_Durczynski](https://discuss.elastic.co/u/Wojciech_Durczynski)\ **Post date:** [January 9, 2012, 2:35pm UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325/3 "2012-01-09T14:35:13Z")
How to do this? Something like: org.elasticsearch.discovery.zen.ping.multicast: ERROR in logging.yml? Won't it mute many other interesting logs? ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 9, 2012, 2:38pm UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325/4 "2012-01-09T14:38:58Z")
Yea, I meant it might make sense to change the level that this failure is logged under..., though, it does help when trying to nail down discovery problems with mixed versions (which is why I put it under WARN to begin with).. 2012/1/9 Wojciech Durczyński [wojciech.durczynski@comarch.com](mailto:wojciech.durczynski@comarch.com) > How to do this? Something like: > org.elasticsearch.discovery.\*\*zen.ping.multicast: ERROR > in logging.yml? Won't it mute many other interesting logs? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:43am UTC](https://discuss.elastic.co/t/eofexception-during-discovery/6325/5 "2017-07-06T03:43:23Z")