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 5A7DF1761F for ; Sat, 27 Jun 2015 14:49:37 +0000 (UTC) Received: (qmail 63450 invoked by uid 500); 27 Jun 2015 14:49:35 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 63381 invoked by uid 500); 27 Jun 2015 14:49:35 -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 63369 invoked by uid 99); 27 Jun 2015 14:49:34 -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:49:34 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.178 as permitted sender) Received: from [209.85.160.178] (HELO mail-yk0-f178.google.com) (209.85.160.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2015 14:47:17 +0000 Received: by ykdr198 with SMTP id r198so81670576ykd.3 for ; Sat, 27 Jun 2015 07:48:20 -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=8O9gdgqEWqg9vTQJZzz+2uzkkfpdyv3wachUZg1ZBcE=; b=eikkj3Q+B71d19J4SlWUroXjdYZTV0mQwZaOA9qy2ub3q4qbbH5uvHau5hzQkLyE0u 8asd1RBs1jf4qxH9DzvyYorjDtEkk7hveDDdIccZjG7GHkzzizwVkwrRg6Fyon4Uammz 4+wr3nnD88rXXzhh+ERI8X5sdPMIPj32zwhb5tp3sYqi30Pih1kH6aoCeailQipvYMCJ USVmElUHTlEqd4uG9pf42VhrP4wOEf9wDVzSckNRf3dSrDlFDOOXlryLqp4cvCsBP5BI BGexwwa2jn+4imLlt4VfPKWvyPRiK1yoelNpdyNkSq11OpjBHxQiFF4ld9RUlDPAfE9R AiYA== MIME-Version: 1.0 X-Received: by 10.170.156.133 with SMTP id x127mr8422430ykc.96.1435416499997; Sat, 27 Jun 2015 07:48:19 -0700 (PDT) Received: by 10.37.208.142 with HTTP; Sat, 27 Jun 2015 07:48:19 -0700 (PDT) In-Reply-To: References: Date: Sat, 27 Jun 2015 07:48:19 -0700 Message-ID: Subject: Re: Hbase master selection doubt From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1139747c9650a1051980f237 X-Virus-Checked: Checked by ClamAV on apache.org --001a1139747c9650a1051980f237 Content-Type: text/plain; charset=UTF-8 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? > --001a1139747c9650a1051980f237--