By the way, another solution would be to downgrade the Hazelcast version (allowing both), but in that case we loose a bunch of enhancements and performance improvements (and bug fixes ;)).

Regards
JB

On 01/21/2015 08:51 AM, Achim Nierbeck wrote:
Hi,
As it used to work without this tweak before it's still a regression. :-)

Regards, Achim

sent from mobile device
Am 21.01.2015 07:36 schrieb "Jean-Baptiste Onofré" <[email protected]>:

It seems that I reproduce the same behavior by disable promisc/multicast
on my network interface. Just disabling multicast and enabling tcp-ip in
etc/hazelcast.xml fixes the problem.

Regards
JB

On 01/21/2015 07:21 AM, Jean-Baptiste Onofré wrote:

Ahhhh I may know.

In previous Hazelcast version, it was possible to enable multicast AND
tcp-ip for joining. Since Hazelcast 3.3.x, it's no more possible.
By default, in the Cellar etc/hazelcast.xml, I enabled multicast and
disable tcp-ip.

If your interface or network doesn't support multicast, it will fail to
discover the nodes.

Can you try to change to tcp-ip (with localhost) instead of multicast ?

Thanks,
Regards
JB

On 01/21/2015 12:15 AM, Achim Nierbeck wrote:

Config seed port is 5701 and cluster size is 1. Some of the ports seem
occupied!



--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com



--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to