Hello Bill, we are running Zk in VMs without problems. Each VM gets an internal IP address (e.g., to talk to its host, like the private range address you have in your log file) and an external IP address (to reach out from the VM host environment, usually also a private one in the 10.x.x.x range). The latter is fixed, the former may change depending on the host where the VM runs and what the DHCP server thinks is available. Consequently, the host name of the VM should be bound to the external IP address.
Additionally, as we generate the Zk config files automatically through centralized provisioning, we use (the external) IP addresses in the config files, rather than host names. There used to be issues with name resolution, so this is safer and changes will be reflected through the provisioning engine, anyway. Cheers, --Jürgen >>>> Hi All >>>> >>>> I am running ZK as a 3 node cluster. Each ZK instance is a VMWare VM in >>>> a >>>> distinct ESX host. Let's assume the three VMs are A, B and C where A is >>>> the >>>> leader. Now if I take down VM B and C and then bring one of them back >>>> up. >>>> However the ZK cluster is never formed unless I bounce VM A. How can I >>>> troubleshoot this? This however does not happen in a physical >>>> environment. >>>> >>>> -- >>>> Cheers >>>> Bill >>>> -- Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С уважением *i.A. Jürgen Wagner* Head of Competence Center "Intelligence" & Senior Cloud Consultant Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543 E-Mail: [email protected] <mailto:[email protected]>, URL: www.devoteam.de <http://www.devoteam.de/> ------------------------------------------------------------------------ Managing Board: Jürgen Hatzipantelis (CEO) Address of Record: 64331 Weiterstadt, Germany; Commercial Register: Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071
