curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Jaton (JIRA)" <>
Subject [jira] [Created] (CURATOR-355) Curator client hangs when connecting to read-only ensemble
Date Mon, 10 Oct 2016 17:10:21 GMT
Benjamin Jaton created CURATOR-355:

             Summary: Curator client hangs when connecting to read-only ensemble
                 Key: CURATOR-355
             Project: Apache Curator
          Issue Type: Bug
          Components: Client
    Affects Versions: 2.11.0
            Reporter: Benjamin Jaton
            Priority: Critical
         Attachments: test2.log

ZK is 3.5.1-alpha

I have a 3 nodes ZK cluster , readonly mode is enabled.
2 nodes are down, so one of them (QA-E8WIN11) is in read-only (verified by using the ZK API
manually). All the machines of the ensemble can be pinged from the client.

I'm using this piece of code:

		Builder curatorClientBuilder = CuratorFrameworkFactory.builder()
				.retryPolicy(new RetryNTimes(3, 5000)).canBeReadOnly(true);

		CuratorFramework client =;
		System.out.println("Successfully established the connection with ZooKeeper");

When curator pick the host that is UP first, it goes through very quickly. When it picks the
host that is down first (QA-E8WIN12), it seems to be stuck at the getData() call for a very
long time, and then eventually fail with a ConnectionLossException. (see attached log)

This message was sent by Atlassian JIRA

View raw message