Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 74F8A17637 for ; Sat, 27 Jun 2015 14:53:56 +0000 (UTC) Received: (qmail 71964 invoked by uid 500); 27 Jun 2015 14:53:54 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 71897 invoked by uid 500); 27 Jun 2015 14:53:54 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 71885 invoked by uid 99); 27 Jun 2015 14:53:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2015 14:53:54 +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 (nike.apache.org: domain of shushantarora09@gmail.com designates 209.85.212.181 as permitted sender) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2015 14:51:39 +0000 Received: by wicnd19 with SMTP id nd19so66188662wic.1 for ; Sat, 27 Jun 2015 07:53:27 -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=5zvt+TzYXctPNHQuTlNRM2bfGNp3ENhhj1ikXQkLtDo=; b=R2HbusR1Pk8vUY/Ouc2H122jgK+Go0xzP0XR/Lm+UoEOawSQQw4IT16SO0GzTSqptD QnT9hPEeGQg2g3jyjv1NWOdBiKZVIx/RVc6ubW/zVFsOAX5Jma9WZjAj/dVVNS0H7nb9 ICG8Qs4JmXDirRy4Hqyh64d9b8/l04ZHpUbBOZyoRsyXBt5+j6K9QtKHRx1s3Tk1lBso hSdciKCSmMEpS6r3A/oKoYJx6k8hnN0TGk8Bqyrpuaqb4U9PWt5ydaaQFQYkmgLkejvF 3jkrMNas1JLsycDmy9hmBdu9AOcYTfqI1XHD9Ky5l8AicOyycuqDjasoK5esMVAqiuPy gnoA== MIME-Version: 1.0 X-Received: by 10.194.200.42 with SMTP id jp10mr13222204wjc.66.1435416807290; Sat, 27 Jun 2015 07:53:27 -0700 (PDT) Received: by 10.28.214.144 with HTTP; Sat, 27 Jun 2015 07:53:27 -0700 (PDT) In-Reply-To: References: Date: Sat, 27 Jun 2015 20:23:27 +0530 Message-ID: Subject: Re: Hbase master selection doubt From: Shushant Arora To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7bb04272e73e0205198104cf X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb04272e73e0205198104cf Content-Type: text/plain; charset=UTF-8 Zookeeper is Sequential Consistency Updates from a client will be applied in the order that they were sent. On Sat, Jun 27, 2015 at 8:18 PM, Ted Yu wrote: > bq. non strictly consistency of Zookeeper > > Can you elaborate on what the above means ? > > please read this: > > http://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#ch_zkGuarantees > > Cheers > > On Sat, Jun 27, 2015 at 7:20 AM, Shushant Arora > > wrote: > > > How Hbase uses Zookeeper for Master selection and region server failure > > detection when Zookeeper is not strictly consistent. > > > > Say In Hbase Master selection process, how does a node is 100 % sure > that a > > master is created ? Does it has to create the /master node and that node > > already exists will thow node exists excpetion . Since only by reading > (ls > > /) . It may get stale data and gets node does not exists.but in actual > > /master was present. > > > > Does there any issue with non strictly consistency of Zookeeper for > Hbase? > > > --047d7bb04272e73e0205198104cf--