A question about connectionTimeout and connection
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- distributed-systems
Research direction
Start by tracing CuratorFrameworkFactory.Builder through connectionTimeoutMs, retryPolicy, and client.start(), then compare that flow with the ZooKeeper connection-loss logs described in the issue. Done means identifying whether repeated connection exceptions match the configured retry and timeout behavior, with a reproducible test or a clearly documented explanation.
Written by the indexing model from the issue text.
Description
Hello, I Use curator as follow:
CuratorFrameworkFactory.Builder builder = CuratorFrameworkFactory.builder()
.connectString("xxx") //this xxx includes 5 invalid IP address.
.sessionTimeoutMs(10_000)
.connectionTimeoutMs(10_000)
retryPolicy(retryNtimes(3,5000));
client.start();
I try to test curator's timeout action when curator first attempt to connect zk server. I think curator(actually internal zookeeper client) will not try to connect server after it retry 3 times and connectionTimeout，but actually I see the log file，zk client seems not controlled by curator? the zk client always throw some exception, such as connectionLossException... never stop until I stop my program.
I use curator not long ago, and try to read curator code. But I still can't understand why curator behavior as described above.
Hope to receive your reply soon.
Thank you.
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/curator
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Upgrade to Jackson 3 Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100