[jira] [Commented] (ZOOKEEPER-1734) Zookeeper fails to connect if one zookeeper host is down on EC2 when using elastic IP (UnknownHostException)
[ 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.(StaticHostProvider.java:60) > > at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:445) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ZOOKEEPER-1734) Zookeeper fails to connect if one zookeeper host is down on EC2 when using elastic IP (UnknownHostException)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751346#comment-13751346 ] Andy Grove commented on ZOOKEEPER-1734: --- Thanks. I have added that link. > 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.(StaticHostProvider.java:60) > > at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:445) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1734) Zookeeper fails to connect if one zookeeper host is down on EC2 when using elastic IP (UnknownHostException)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746063#comment-13746063 ] Edward Ribeiro commented on ZOOKEEPER-1734: --- I suggest to put at least a "related to" link between the two JIRAs. PS: I am tackling this issue. > 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.(StaticHostProvider.java:60) > > at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:445) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1734) Zookeeper fails to connect if one zookeeper host is down on EC2 when using elastic IP (UnknownHostException)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744610#comment-13744610 ] Edward Ribeiro commented on ZOOKEEPER-1734: --- This issue is sort of a duplicate of https://issues.apache.org/jira/browse/ZOOKEEPER-1576 > 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.(StaticHostProvider.java:60) > > at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:445) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
