Multicast between two versions with different cluster names


(David Pilato) #1

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 :

Thanks for your help
David.

--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet


(Shay Banon) #2

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 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 :

Thanks for your help

David.

--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet


(wvdklee) #3

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
elastic search 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 <javascript:> <
da...@pilato.fr <javascript:>> 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 :

Thanks for your help

David.

--
David Pilato
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.
For more options, visit https://groups.google.com/groups/opt_out.


(David Pilato) #4

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
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 8 oct. 2013 à 16:04, wvdklee 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 elastic search 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 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 :

Thanks for your help
David.

--
David Pilato
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #5