Prior to Curator 3.0.0, LOST meant that the retry policy had expired. However in 3.0.0, LOST now means that the ZK session has expired. See here: http://curator.apache.org/errors.html
==================== Jordan Zimmerman > On Dec 4, 2015, at 11:59 AM, Alvaro Gareppe <[email protected]> wrote: > > I want to be able to say to curator retry to connect to zookeeper 4 times > even tough my operations have an unlimited retry policy. > > Why? because when I say RetryPolicy = retry forever and zookeeper dies > > I get (as expected) a connection event = SUSPENDED in the connection > listener, but after a while I dont get a LOST event that I expect even tough > the session is dead and the ephemeral nodes are gone... I'm using that LOST > state to know that my ephemeral nodes are gone cause if not I want to kill > the connection > > Maybe there is a way without a connection policy (asuming that dotn exist)... > > So at the end my question is.. how to now when the connection its in a state > where you are reconnected but all your ephemeral nodes are gone? cause I > thought that LOST was that state.. but there are cases where I'm not getting > that > > > >> On Fri, Dec 4, 2015 at 1:30 PM, Jordan Zimmerman >> <[email protected]> wrote: >> What would that mean? I don't understand the difference. >> >> ==================== >> Jordan Zimmerman >> >>> On Dec 4, 2015, at 11:23 AM, Alvaro Gareppe <[email protected]> wrote: >>> >>> Its there a way to configure the reconnetion policy in curator ? >>> >>> Meaning.. "what to do on connection lost ? " >>> >>> Cause now there is a retry policy.. but the connection its always re >>> attempted. >>> >>> -- >>> Ing. Alvaro Gareppe >>> [email protected] > > > > -- > Ing. Alvaro Gareppe > [email protected]
