A few things to try:
Integer.MAX_VALUE is not very useful for the session/connection timeouts. Try
reasonable numbers.
The call to client.blockUntilConnected() isn't needed, remove it
Other than that, I'd need to see logs to see why ZooKeeper itself isn't
connecting.
-JZ
> On Dec 7, 2018, at
Absolutely, I just wanted to give the high-level description in case this
was a clear anti-pattern (multiple threads connecting concurrently to ZK on
localhost).
Each thread has its own Curator client right now because of the design of
Kafka Connect--Connect "tasks", which run on separate
There isn't much to go on in your description. Please send some sample code,
logs, possibly a thread dump. Maybe send your test program. One thing that
sticks out is that you say each thread has its own Curator client. Why is that?
You only need 1 Curator client per ZK ensemble in a VM.
I ran into what looks like a deadlock in blockUntilConnected and wanted to
give a high-level description in case someone can help me debug the issue.
I can try to make a reproducible example, but for reasons that will be
apparent, that's not straightforward.
I am using Curator within a custom
