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 8D66111F58 for ; Sat, 14 Jun 2014 21:11:25 +0000 (UTC) Received: (qmail 10905 invoked by uid 500); 14 Jun 2014 21:11:22 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 10824 invoked by uid 500); 14 Jun 2014 21:11:22 -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 10812 invoked by uid 99); 14 Jun 2014 21:11:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jun 2014 21:11:22 +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 sahmed1020@gmail.com designates 209.85.160.180 as permitted sender) Received: from [209.85.160.180] (HELO mail-yk0-f180.google.com) (209.85.160.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jun 2014 21:11:17 +0000 Received: by mail-yk0-f180.google.com with SMTP id 131so3066444ykp.25 for ; Sat, 14 Jun 2014 14:10: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:from:date:message-id:subject:to :content-type; bh=AK6AX1w0ORCBojJoEhQPBsveMkhJFFG1HSCzzVNm0ok=; b=ZJzhZO/DdXD4XAsTb1Lg6xpqYofvCFg3ab+Toj23eHV3dfL0QxFCW4dsCbLJYdqiNQ H09zbdzVc+n1W3hQWNDFbh4kmguety/7BTcz59tPaQsw/FCAL4nJHtg0jtqnSIaksq8Q WoHgrp+U1I3+BLnxpc6QJKz7eEffTghXEiHpAPHYfHLQb2yUecV520xhOB45jz/Cm63E qJkp56TdIDcWmQLwlc9u7M5HmQy70s1m4aJQkznRe0RSMhJ1wy49N+x8inniTOnXN+dK Bzs8J79rjhyBK3Wz5bR/wJHfMwm5VLiGOQnRMo6tS6us2rnuIF9/mrZIJcitJQ9+w+sI +SQQ== X-Received: by 10.236.159.67 with SMTP id r43mr18458717yhk.50.1402780256455; Sat, 14 Jun 2014 14:10:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.98.65 with HTTP; Sat, 14 Jun 2014 14:10:36 -0700 (PDT) In-Reply-To: References: From: S Ahmed Date: Sat, 14 Jun 2014 17:10:36 -0400 Message-ID: Subject: Re: if/when zookeeper goes down, how to recover? To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf30434c64e2504604fbd23acc X-Virus-Checked: Checked by ClamAV on apache.org --20cf30434c64e2504604fbd23acc Content-Type: text/plain; charset=UTF-8 Are there any 'best practices' when running zookeeper on ec2? i.e. the latency could be poor and hostname/ip addresses can also change when bring a node up/down. On Sat, Jun 14, 2014 at 10:13 AM, Ted Yu wrote: > bq. what is the process do recover? > > You need to bring zookeeper nodes back as soon as possible. > > bq. will all clients reconnect or do you have to restart all servers? > > This depends on the release of hbase you're using and the duration which > zookeeper ensemble is down. > If the duration is longer than the value for zookeeper.session.timeout, > region servers would go down. > > See also http://hbase.apache.org/book.html#zookeeper > > > On Sat, Jun 14, 2014 at 6:31 AM, S Ahmed wrote: > > > Hello, > > > > If zookeeper goes down (all of them if you have 3/5 nodes), what is the > > process do recover? > > > > If you simply bring back the zookeeper nodes, will all clients reconnect > or > > do you have to restart all servers? > > > > Thanks. > > > --20cf30434c64e2504604fbd23acc--