# Multicast between two versions with different cluster names **URL:** \ **Category:** Elasticsearch\ **Created:** [November 25, 2011, 10:34am UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971 "2011-11-25T10:34:12Z")\ **Posts on this page:** 5\ **Page:** 1
**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:** [November 25, 2011, 10:34am UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971/1 "2011-11-25T10:34:12Z")
Hi there, Here is my problem. Let say we are 2 developpers on the same LAN. Dev 1 is running ES 0.17.10 with clustername = clusterdev1 Dev 2 wantsto run ES 0.18.4 with clustername = clusterdev2 As you can see, cluster names are differents. When I start the Dev 2 node, I get : [2011-11-25 11:21:30,606][WARN][discovery.zen.ping.multicast] [Bob Diamond] failed to read requesting node from /10.115.1.75: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:51) 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) Should I : - only change the log level to ERROR fororg.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing ? - modify the default config to isolate nodes ? - file a bug on github ? (not sure it's the same issue as [https://github.com/elasticsearch/elasticsearch/issues/1443](https://github.com/elasticsearch/elasticsearch/issues/1443) ) Thanks for your help David. -- David Pilato [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) Twitter : @dadoonet ---
**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:** [November 27, 2011, 3:17pm UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971/2 "2011-11-27T15:17:37Z")
Yes, the exception might happen because the format of the multicast message changed. In 0.18, I started with an effort to try and solve this (and other version related issues) by associating a version with a node when it gets serialized. This will help in the future, though its not fully there yet... On Fri, Nov 25, 2011 at 12:34 PM, [david@pilato.fr](mailto:david@pilato.fr) [david@pilato.fr](mailto:david@pilato.fr) wrote: > \*\* > > Hi there, > > Here is my problem. > > Let say we are 2 developpers on the same LAN. > > Dev 1 is running ES 0.17.10 with clustername = clusterdev1 > > Dev 2 wants to run ES 0.18.4 with clustername = clusterdev2 > > As you can see, cluster names are differents. > > When I start the Dev 2 node, I get : > > [2011-11-25 11:21:30,606][WARN][discovery.zen.ping.multicast] [Bob > Diamond] failed to read requesting node from /10.115.1.75: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:51) > 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) > > ``` > > Should I : > > - only change the log level to ERROR for org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > ? > > - modify the default config to isolate nodes ? > > - file a bug on github ? (not sure it's the same issue as > [Cluster configuration EC2 not functioning · Issue #1443 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1443) ) > > Thanks for your help > > David. > > -- > David Pilato > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet ---
**Author:** ![wvdklee](https://avatars.discourse-cdn.com/v4/letter/w/a88e4f/32.png) [@wvdklee](https://discuss.elastic.co/u/wvdklee)\ **Post date:** [October 8, 2013, 2:04pm UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971/3 "2013-10-08T14:04:49Z")
Hello, I have just received the same issue as David. My colleague is running the latest trunk version and I am running 0.90.2 on the same network. However, despite us both having different cluster/node names I am unable to start my Elasticsearch server, due to the MulticastZenPing error. Is this issue still waiting in the pipeline for a fix? Wayne On Sunday, November 27, 2011 3:17:37 PM UTC, kimchy wrote: > Yes, the exception might happen because the format of the multicast > message changed. In 0.18, I started with an effort to try and solve this > (and other version related issues) by associating a version with a node > when it gets serialized. This will help in the future, though its not fully > there yet... > > On Fri, Nov 25, 2011 at 12:34 PM, [da...@pilato.fr](mailto:da...@pilato.fr) \ \< > [da...@pilato.fr](mailto:da...@pilato.fr) \\> wrote: > > > \*\* > > > > Hi there, > > > > Here is my problem. > > > > Let say we are 2 developpers on the same LAN. > > > > Dev 1 is running ES 0.17.10 with clustername = clusterdev1 > > > > Dev 2 wants to run ES 0.18.4 with clustername = clusterdev2 > > > > As you can see, cluster names are differents. > > > > When I start the Dev 2 node, I get : > > > > [2011-11-25 11:21:30,606][WARN][discovery.zen.ping.multicast] [Bob > > Diamond] failed to read requesting node from /10.115.1.75: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:51) > > 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) > > > > ``` > > > > Should I : > > > > - only change the log level to ERROR for org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > ? > > > > - modify the default config to isolate nodes ? > > > > - file a bug on github ? (not sure it's the same issue as > > [Cluster configuration EC2 not functioning · Issue #1443 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1443) ) > > > > Thanks for your help > > > > David. > > > > -- > > David Pilato > > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > > Twitter : @dadoonet -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [October 8, 2013, 2:13pm UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971/4 "2013-10-08T14:13:34Z")
Could you try with elasticsearch 0.90.5 and master? I guess some stuff has been fixed from 0.90.2 about serialization. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 8 oct. 2013 à 16:04, wvdklee [wayne.vandeklee@gmail.com](mailto:wayne.vandeklee@gmail.com) a écrit : > Hello, > > I have just received the same issue as David. My colleague is running the latest trunk version and I am running 0.90.2 on the same network. However, despite us both having different cluster/node names I am unable to start my Elasticsearch server, due to the MulticastZenPing error. Is this issue still waiting in the pipeline for a fix? > > Wayne > > On Sunday, November 27, 2011 3:17:37 PM UTC, kimchy wrote: > Yes, the exception might happen because the format of the multicast message changed. In 0.18, I started with an effort to try and solve this (and other version related issues) by associating a version with a node when it gets serialized. This will help in the future, though its not fully there yet... > > On Fri, Nov 25, 2011 at 12:34 PM, [da...@pilato.fr](mailto:da...@pilato.fr) [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > Hi there, > > Here is my problem. > Let say we are 2 developpers on the same LAN. > Dev 1 is running ES 0.17.10 with clustername = clusterdev1 > Dev 2 wants to run ES 0.18.4 with clustername = clusterdev2 > > As you can see, cluster names are differents. > > When I start the Dev 2 node, I get : > [2011-11-25 11:21:30,606][WARN][discovery.zen.ping.multicast] [Bob Diamond] failed to read requesting node from /10.115.1.75: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:51) > 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) > > Should I : > > - only change the log level to ERROR for org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing ? > - modify the default config to isolate nodes ? > - file a bug on github ? (not sure it's the same issue as [Cluster configuration EC2 not functioning · Issue #1443 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1443) ) > > Thanks for your help > David. > > -- > David Pilato > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:13am UTC](https://discuss.elastic.co/t/multicast-between-two-versions-with-different-cluster-names/5971/5 "2017-07-06T02:13:21Z")