Apache's JIRA Issue Tracker | Tally Tsabary | 4 years ago
  1. 0

    Using a cluster of three 3.4.3 zookeeper servers. All the servers are up, but on the client machine, the firewall is blocking one of the servers. The following exception is happening, and the client is not connected to any of the other cluster members. The exception:Nov 02, 2012 9:54:32 PM logError SEVERE: Background exception was not retry-able or retry gave up at Method) at$1.lookupAllHostAddr(Unknown Source) at Source) at Source) at Source) at Source) at org.apache.zookeeper.client.StaticHostProvider.<init>( at org.apache.zookeeper.ZooKeeper.<init>( at org.apache.zookeeper.ZooKeeper.<init>( The code at the org.apache.zookeeper.client.StaticHostProvider.<init>( is : public StaticHostProvider(Collection<InetSocketAddress> serverAddresses) throws UnknownHostException { for (InetSocketAddress address : serverAddresses) { InetAddress resolvedAddresses[] = InetAddress.getAllByName(address .getHostName()); for (InetAddress resolvedAddress : resolvedAddresses) { this.serverAddresses.add(new InetSocketAddress(resolvedAddress .getHostAddress(), address.getPort())); } } ...... The for-loop is not trying to resolve the rest of the servers on the list if there is an UnknownHostException at the InetAddress.getAllByName(address.getHostName()); and it fails the client connection creation. I was expecting the connection will be created for the other members of the cluster. Also, InetAddress is a blocking command, and if it takes very long time, (longer than the defined timeout) - that also should allow us to continue to try and connect to the other servers on the list. Assuming this will be fixed, and we will get connection to the current available servers, I think the zookeeper should continue to retry to connect to the not-connected server of the cluster, so it will be able to use it later when it is back. If one of the servers on the list is not available during the connection creation, then it should be retried every x time despite the fact that we

    Apache's JIRA Issue Tracker | 4 years ago | Tally Tsabary
  2. 0

    Titan 0.5.3 Hangs while connecting to Hbase 0.98.4 with HDP 2.2 stack

    GitHub | 2 years ago | bala-infini (""): Name or service not known
  3. 0

    [#DISTRO-578] Can't recover a zookeeper connection failure - Cloudera Open Source | 2 years ago
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Endless recursive call when the ZK quorum spec is invalid

    GitHub | 5 years ago | tsuna tmpzookeeper
  6. 0

    kafka cant connect to zookeeper- FATAL Fatal error during KafkaServerStable startup

    Stack Overflow | 3 years ago | Tampa
    org.I0Itec.zkclient.exception.ZkException: Unable to connect to,

  1. Raggyman 2 times, last 4 weeks ago
  2. Nikolay Rybak 1 times, last 3 months ago
  3. pranavprakash 1 times, last 2 days ago
  4. davidvanlaatum 6 times, last 1 week ago
  5. tvrmsmith 2 times, last 1 month ago
31 more registered users
46 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis


  2. Java RT
    1. Method)
    2.$1.lookupAllHostAddr(Unknown Source)
    3. Source)
    4. Source)
    5. Source)
    6. Source)
    6 frames
  3. Zookeeper
    1. org.apache.zookeeper.client.StaticHostProvider.<init>(
    2. org.apache.zookeeper.ZooKeeper.<init>(
    3. org.apache.zookeeper.ZooKeeper.<init>(
    3 frames