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 7A7ED9132 for ; Tue, 27 Sep 2011 23:51:45 +0000 (UTC) Received: (qmail 88328 invoked by uid 500); 27 Sep 2011 23:51:45 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 88296 invoked by uid 500); 27 Sep 2011 23:51:45 -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 88286 invoked by uid 500); 27 Sep 2011 23:51:45 -0000 Delivered-To: apmail-hadoop-zookeeper-user@hadoop.apache.org Received: (qmail 88282 invoked by uid 99); 27 Sep 2011 23:51:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Sep 2011 23:51:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ishaaq@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Sep 2011 23:51:37 +0000 Received: by fxd23 with SMTP id 23so61180fxd.35 for ; Tue, 27 Sep 2011 16:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=odR2ERtCX0wYCw12P3Hdn/jxwLv5hkXpRFtz+sRcFb0=; b=bCM3EhfYt2M3zXyYDYyRuSacSoC78ppXDD6gbB1TA4yNULKZiAOQYHkzjbFAOpClyV KVob1bmrwyAEuoZ/WpjePcZMalwYpucjlR+a7r14zI1K+lrtiCqBiNnw718AMC0alr1G N7kcoA6qbBeZOYI/u/c/GIQT26eN+9YLhtDP0= MIME-Version: 1.0 Received: by 10.223.35.202 with SMTP id q10mr620831fad.138.1317167474166; Tue, 27 Sep 2011 16:51:14 -0700 (PDT) Received: by 10.223.98.207 with HTTP; Tue, 27 Sep 2011 16:51:14 -0700 (PDT) Date: Wed, 28 Sep 2011 09:51:14 +1000 Message-ID: Subject: ephemerals on ZK failure From: Ishaaq Chandy To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001517473544684d3e04adf4f35a X-Virus-Checked: Checked by ClamAV on apache.org --001517473544684d3e04adf4f35a Content-Type: text/plain; charset=ISO-8859-1 Hi, What is the expected behaviour of ephemerals on disconnects? Suppose a client creates an ephemeral and then, some time later, we have a network failure, or ZK shuts down/crashes. During this downtime, the client JVM is still up and running. What happens when the ZK connection is re-established, does the ephemeral get automatically recreated or does the client have to make an explicit call to recreate it? Thanks, Ishaaq --001517473544684d3e04adf4f35a--