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 7D94DDA6D for ; Mon, 24 Jun 2013 22:22:23 +0000 (UTC) Received: (qmail 13965 invoked by uid 500); 24 Jun 2013 22:22:22 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 13894 invoked by uid 500); 24 Jun 2013 22:22:22 -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 13886 invoked by uid 99); 24 Jun 2013 22:22:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jun 2013 22:22:22 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bitanarch@gmail.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jun 2013 22:22:17 +0000 Received: by mail-ie0-f170.google.com with SMTP id e11so26481880iej.1 for ; Mon, 24 Jun 2013 15:21:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iFTIrnud5gLhCYwwRmUvQimSKYcCqch8EjLMLurK77U=; b=tvL0Uhdk2uB7/D8Wfp2n37WnHRjWJs6E4uwaVhJh0Po4zzuN9/RWMdl5ab7tDJX3OJ zO+x8Q96f6ZgsG+a2a1VrU3eeGiWNPJc30w8iRx2VO5bQUrROjjY+L/P7oBfZmOGHhh9 meoJ6JrZK721BT3pXD0btV31rawkSEpeKezCjJvqwQPdQiYHrZd8ikntL3m32+gA8hZy oSBQ06BnWbiY/a6UZyZ7jmDZ0WO4L7J1pKa97p/x4psHz4Vy2iHSYHKrdJ8snIB2ssq/ FLlAqfTg579Kzbet3MN6/q7MjZ43qZbM3VBmiJ3ngH7JkG2HamWB8RN6yXfqar5tvdKU GVew== MIME-Version: 1.0 X-Received: by 10.42.226.136 with SMTP id iw8mr8996088icb.88.1372112516349; Mon, 24 Jun 2013 15:21:56 -0700 (PDT) Received: by 10.50.15.202 with HTTP; Mon, 24 Jun 2013 15:21:56 -0700 (PDT) In-Reply-To: <1372077331171-7578790.post@n2.nabble.com> References: <1372077331171-7578790.post@n2.nabble.com> Date: Mon, 24 Jun 2013 15:21:56 -0700 Message-ID: Subject: Re: Determine when ZooKeeper Instance is in-sync From: Martin Kou To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=001a11c31ddc2105d204dfedd7ad X-Virus-Checked: Checked by ClamAV on apache.org --001a11c31ddc2105d204dfedd7ad Content-Type: text/plain; charset=ISO-8859-1 Try telnet'ing to the ZooKeeper server and run the 'stat' command there. It'll tell you whether it's ready serving request or not. Best Regards, Martin Kou On Mon, Jun 24, 2013 at 5:35 AM, grayaii wrote: > How do you determine when a follower has finished syncing all its data? > For instance, if your data dir is huge, it will take some time for the data > transfer to complete. > How do you know when it has finished? > Thanks! > > > > -- > View this message in context: > http://zookeeper-user.578899.n2.nabble.com/Determine-when-ZooKeeper-Instance-is-in-sync-tp7578790.html > Sent from the zookeeper-user mailing list archive at Nabble.com. > --001a11c31ddc2105d204dfedd7ad--