[
https://issues.apache.org/jira/browse/CURATOR-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Grove updated CURATOR-40:
------------------------------
Description:
We use DNS names to specify Zookeeper host names. If one of the ZK hosts shuts
down or loses network connectivity we can no longer connect via Curator, even
though the other ZK hosts are still running and have quorum. The issue is
specific to an UnknownHostException being thrown on DNS resolution when calling
the start() method on CuratorZookeeperClient.
I have attached a unit test which demonstrates the issue and provides more
detail in the comments.
was:
We use DNS names to specify Zookeeper host names. If one of the ZK hosts shuts
down or loses network connectivity we can no longer connect via Curator, even
though the other ZK hosts are still running and have quorum. The issue is
specific to an UnknownHostException being thrown on DNS resolution when calling
the start() method on CuratorZookeeperClient.
> Curator client does cannot connect after one zookeeper host shuts down on EC2
> -----------------------------------------------------------------------------
>
> Key: CURATOR-40
> URL: https://issues.apache.org/jira/browse/CURATOR-40
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.0.1-incubating
> Environment: Ubuntu instances on Amazon EC2 using DNS host names
> Reporter: Andy Grove
> Attachments: ApacheCuratorUnknownHostTest.java
>
>
> We use DNS names to specify Zookeeper host names. If one of the ZK hosts
> shuts down or loses network connectivity we can no longer connect via
> Curator, even though the other ZK hosts are still running and have quorum.
> The issue is specific to an UnknownHostException being thrown on DNS
> resolution when calling the start() method on CuratorZookeeperClient.
> I have attached a unit test which demonstrates the issue and provides more
> detail in the comments.
--
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
