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 0C684F2BE for ; Fri, 5 Jul 2013 13:37:05 +0000 (UTC) Received: (qmail 83278 invoked by uid 500); 5 Jul 2013 13:37:04 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 83067 invoked by uid 500); 5 Jul 2013 13:37:03 -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 83051 invoked by uid 99); 5 Jul 2013 13:37:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 13:37:02 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of habi123@gmail.com designates 209.85.128.182 as permitted sender) Received: from [209.85.128.182] (HELO mail-ve0-f182.google.com) (209.85.128.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 13:36:58 +0000 Received: by mail-ve0-f182.google.com with SMTP id ox1so1780719veb.41 for ; Fri, 05 Jul 2013 06:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=EKckpV7waY3TAS/mYMpd8/CnH/pMvk++RVvku/rIzes=; b=yE9UImG+hsaRI2vPI3pVqC9w0xJ/ULbt9fCqlJ8WdkfAwC2GG1SQ7GUYgPBdoVK4sv DBID2DiCfhhRyjJE4+mnxO79OI+ZqHF59766jsOx7etbIdjpoCr6Qrm7SW8T9NwUjN7b NPrLI10MkYZAwk3ngyWTsOr7dfH4ZJ/lB8Wgr0zb7jOIByW3m30EnWHZavmrGjUOV85O ypNhuyGH8xLnsRTAKJyVeQmTtKBVG14eAq+m+27pj8rXWYXLggEaD7Stw3yDrICT2RA4 XKDADfycNZ+wR8rC6G1BRyr99QZXnjXgMMbHxARlSv8nNhU4AnAH3m3aEDSrhl+q57p9 mqig== X-Received: by 10.220.168.141 with SMTP id u13mr6765883vcy.23.1373031397468; Fri, 05 Jul 2013 06:36:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.255.9 with HTTP; Fri, 5 Jul 2013 06:36:17 -0700 (PDT) From: H A B E E B Date: Fri, 5 Jul 2013 19:06:17 +0530 Message-ID: Subject: question on data expiry To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=001a11c24f56b6367104e0c3c817 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c24f56b6367104e0c3c817 Content-Type: text/plain; charset=ISO-8859-1 (I could not find an answer anywhere hence looking for help here) This is a multi region setup, where leader/follower is one region and observers in another 2 regions. We recently had an issue with the inter region connectivity where the observers were not able to contact the leader. At the same time we happened to notice that new connection to 'zookeeper observer' started failing and we logged in to the zkCli.sh and did ls / there was no data. Is this expected? Is there anyway we can control the expiry? Once the inter region connectivity was restored, the 'zookeeper observer' picked up the latest snapshot from the leader. Is there any best practices which could withstand a WAN failure? Thanks for help, --001a11c24f56b6367104e0c3c817--