ConnectionStateListener

[DP]

Hi,

Currently I have an application with 8 instances and a zookeeper cluster with 5 and am using Curator, I noticed that ConnectionStateListener enters a SUSPEND state and then RECONNECTED and also LOST to RECONNECTED and I can not understand why this happens.

my client configuration is: 

CuratorFrameworkFactory.builder().connectString(ConnectionString)

            .retryPolicy(new RetryNTimes(0, 0)).threadFactory(new ThreadFactoryBuilder().setDaemon(true).build())

        .sessionTimeoutMs(1000).connectionTimeoutMs(1000).build();

and we are using Curator recipes (1.3.1) to perform a distributed locking.

could anyone help?

thanks.

[Jordan Zimmerman]

Curator goes to SUSPENDED when Disconnected is received. This can happen for a variety of reasons: network partition, the server you're connected to goes down, etc. If Curator received SysConnected it will then go to RECONNECTED. However if it receives, Expired or the connection timeout expires it will go to LOST. Curator, however, will continue to try to connect which can then result in RECONNECTED.

See here for details:

http://curator.incubator.apache.org/errors.html

-Jordan

--
You received this message because you are subscribed to the Google Groups "curator-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to curator-user...@googlegroups.com.
To post to this group, send email to curato...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/curator-users/-/GChMUMve9tgJ.
For more options, visit https://groups.google.com/groups/opt_out.