[
https://issues.apache.org/jira/browse/ZOOKEEPER-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062357#comment-14062357
]
Benjamin Jaton commented on ZOOKEEPER-1734:
-------------------------------------------
https://issues.apache.org/jira/browse/ZOOKEEPER-1846 is a possible duplicate.
The issue also frequently happens with VMs.
> Zookeeper fails to connect if one zookeeper host is down on EC2 when using
> elastic IP (UnknownHostException)
> ------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1734
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1734
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.5
> Environment: Amazon EC2. Linux.
> Reporter: Andy Grove
>
> We use Amazon Elastic IP for zookeeper hosts so that the zookeeper hosts have
> the same IP address after a restart.
> The issue is, if one host is down then we cannot connect to the other hosts.
> Here is an example connect string:
> "ec2-1-2-3-4.compute-1.amazonaws.com, ec2-4-3-2-1.compute-1.amazonaws.com,
> ec2-5-5-5-5.compute-1.amazonaws.com"
> If all three hosts are up, we can connect. If one host is down, then we
> cannot create a Zookeeper instance due to an UnknownHost exception, even
> though the other servers in the connect string are valid.
> java.net.UnknownHostException: ec2-5-5-5-5.compute-1.amazonaws.com
> at java.net.InetAddress.getAllByName0(InetAddress.java:1243)
> at java.net.InetAddress.getAllByName(InetAddress.java:1155)
> at java.net.InetAddress.getAllByName(InetAddress.java:1091)
> at
> org.apache.zookeeper.client.StaticHostProvider.<init>(StaticHostProvider.java:60)
>
> at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:445)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
