Can I chime and say that 3.4.6 (as of 2 days ago) did not work us? We switched from 3.4.5 and our servers couldnt connect to each other. On Wed, Mar 5, 2014 at 1:21 PM, Flavio Junqueira <[EMAIL PROTECTED]>wrote:
Dont have the logs available but it I think it was related to the binding address. In 3.4.5 I see that it binds to 0.0.0.0.0 whereas in the 3.4.6 it was binding to machine-name/10.0.12.100 (some internal ip) On Thu, Mar 20, 2014 at 4:33 AM, FPJ <[EMAIL PROTECTED]> wrote:
Perhaps you could reproduce and send the logs and config files? Also include some detail about the environment would be helpful. Windows is quite different from linux for example. The more information you provide the more likely we'll be able to get to the bottom of the issue.
On Thu, Mar 20, 2014 at 10:13 AM, Software Dev <[EMAIL PROTECTED]> wrote:
I am going to follow up on that thread since I ran into the same problem, and it is indeed related to ZOOKEEPER-1096.
Basically I used to use the hostname in my zoo.cfg, which under Ubuntu, resolves to 127.0.1.1. So all of a sudden, upgrading ZK made my server invisible to the other machines.
I remember running into that same issue with OpenMQ as well, and they explicitely mention it in their documentation: *In particular, some Linux installers automatically set the local host to a loopback network address, most commonly 127.0.0.1. On such systems, you must do the following: For each Linux system participating in the cluster, check the /etc/hosts file as part of cluster setup. If the system uses a static IP address, edit the /etc/hosts file to specify the correct address for the local host. If the address is registered with Domain Name Service (DNS), edit the file /etc/nsswitch.conf so that DNS lookup is performed before consulting the local hosts file.* http://docs.oracle.com/cd/E18930_01/html/821-2438/aeohz.html#aeoia
Then I found out about the magical option *quorumListenOnAllIPs=true* to be added in zoo.cfg. I think this option should be kept not only for backward compatibility but also because it can be really useful in some deployments.
Best, Ben On Thu, Mar 20, 2014 at 1:16 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext