It can't. When the connection is restored, you will either get the pending notifications or a session expired message.
On Mon, Jul 8, 2013 at 6:10 AM, Prasad GS <[email protected]> wrote: > Any idea about #1 : When the connection is not available, how can zookeeper > send session events to outstanding watch handlers? > > > On Mon, Jul 8, 2013 at 5:55 PM, Chris Brinley < > [email protected] > > wrote: > > > Your local client detects session drop. That is tcp connection lost. By > > safe mode all that is meant is that your application should take action > to > > deal with this new state (I. E. No connection to zookeeper cluster). In > > this mode it may not be advisable to handle new requests or allow > > configuration changes. This depends on the rules of the problem domain if > > course. > > ________________________________________ > > From: Prasad GS [[email protected]] > > Sent: Monday, July 08, 2013 7:11 AM > > To: [email protected] > > Subject: help regarding zookeeper watches > > > > Hi, > > > > As per the zookeeper programmers guide regarding watches, > > > > "When you disconnect from a server (for example, when the server fails), > > you will not get any watches until the connection is reestablished. For > > this reason session events are sent to all outstanding watch handlers. > Use > > session events to go into a safe mode: you will not be receiving events > > while disconnected, so your process should act conservatively in that > mode" > > > > We have couple of questions here : > > > > 1. When the connection is not available, how can zookeeper send session > > events to outstanding watch handlers? > > 2. Can someone please elaborate the safe mode & the steps that needs to > be > > done in that mode > > > > Regards, > > Skanda > > >
