FYI, one user in my company is using Netflix Curator 1.3.4. This behavior
might be changed in Apache Curator.

The client was set up the connection string with five instances but two
instances were not reachable. My theory is, it shouldn't get ConnectionLoss
after Curator had been initialized but it was throwing ConnectionLoss
exceptions almost once per minute. Its connection timeout is 30 seconds.

Is this normal behavior? Or is this known issue fixed in Apache Curator?

Thank you
Best, Jae

Reply via email to