Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB9EE1058A for ; Mon, 8 Jul 2013 12:26:12 +0000 (UTC) Received: (qmail 6599 invoked by uid 500); 8 Jul 2013 12:26:11 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 6573 invoked by uid 500); 8 Jul 2013 12:26:11 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 6565 invoked by uid 99); 8 Jul 2013 12:26:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 12:26:11 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Chris.Brinley@morningstar.com designates 64.18.2.161 as permitted sender) Received: from [64.18.2.161] (HELO exprod7og104.obsmtp.com) (64.18.2.161) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 12:26:03 +0000 Received: from MSEXET81.morningstar.com ([216.228.224.45]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUdqvxbehjzKMgrmNVkVFJF5bh6H6A6sB@postini.com; Mon, 08 Jul 2013 05:25:42 PDT Received: from MSEXCHM84.morningstar.com (172.28.13.44) by MSEXET81.morningstar.com (172.28.6.45) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 8 Jul 2013 07:25:40 -0500 Received: from MSEXCHM81.morningstar.com ([fe80::b102:6618:6e80:4bb8]) by MSEXCHM84.morningstar.com ([fe80::a162:cbe6:e897:46fa%20]) with mapi id 14.03.0123.003; Mon, 8 Jul 2013 07:25:40 -0500 From: Chris Brinley To: "user@zookeeper.apache.org" Subject: RE: help regarding zookeeper watches Thread-Topic: help regarding zookeeper watches Thread-Index: AQHOe9RWhEKRi2uq0E28yp4PAkVxEJlas6iM Date: Mon, 8 Jul 2013 12:25:38 +0000 Message-ID: <89870D362F826B42868979F2760F7BD50E7809@MSEXCHM81.morningstar.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [98.222.113.41] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Your local client detects session drop. That is tcp connection lost. By saf= e mode all that is meant is that your application should take action to dea= l with this new state (I. E. No connection to zookeeper cluster). In this m= ode it may not be advisable to handle new requests or allow configuration c= hanges. This depends on the rules of the problem domain if course.=20 ________________________________________ From: Prasad GS [gsp200183@gmail.com] Sent: Monday, July 08, 2013 7:11 AM To: user@zookeeper.apache.org 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