curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Grove (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CURATOR-40) Curator client does cannot connect after one zookeeper host shuts down on EC2
Date Tue, 25 Jun 2013 20:59:19 GMT
Andy Grove created CURATOR-40:
---------------------------------

             Summary: 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


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.



--
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

Mime
View raw message