I know it would be so hard to reproduce. In the case that curator totally loses the connection, is it possible to lose the watcher? The only difference between old implementation and the current one is, I guess, ConnectionStateListener will be kicked in regardless of watcher but watcher can be gone.
On Sun, Mar 16, 2014 at 6:47 PM, Jordan Zimmerman < [email protected]> wrote: > I just created a test to try to reproduce and it works correctly. I've > reviewed the code and don't see where it can go wrong. > > https://gist.github.com/anonymous/9592593 > > -JZ > > > From: Bae, Jae Hyeon [email protected] > Reply: [email protected] [email protected] > Date: March 16, 2014 at 8:15:02 PM > To: [email protected] [email protected] > Subject: Why ConnectionStateListener was removed from > PersistentEphemeralNode? > > Hi > > I am using PersistentEphemeralNode recipe very actively. I observed > PersistentEphemeralNode was not reinstated on zookeeper outage and I am > wondering that why ConnectionStateLister was removed because the old > version of PersistentEphemeralNode successfully reinstated its node. > > So, I am willing to override its implementation with old version. > > Thank you > Best, Jae > >
