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 5DAA66742 for ; Tue, 19 Jul 2011 07:03:16 +0000 (UTC) Received: (qmail 41369 invoked by uid 500); 19 Jul 2011 07:03:15 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 40859 invoked by uid 500); 19 Jul 2011 07:03:02 -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 40845 invoked by uid 99); 19 Jul 2011 07:02:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2011 07:02:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of weihua.jiang@gmail.com designates 74.125.83.169 as permitted sender) Received: from [74.125.83.169] (HELO mail-pv0-f169.google.com) (74.125.83.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2011 07:02:49 +0000 Received: by pvc12 with SMTP id 12so4550105pvc.14 for ; Tue, 19 Jul 2011 00:02:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sGQX2atJZZjJldOjdC15q5h3I1RctdPiu8InMU2vYcI=; b=av8LSLjzQIZ1bV5sjxmcudThgyt4T1UqJsVlhLGxigZge6kJEIxO0snoghA8z5vIVn 7dTcUjqNF48ogqEznPUOZ9mzlid0s3H3SLZuICwG+qgKjwUx46LpSWtZvh02QLtxk7Hk e8tQQfEaOKh7mWScgXtk9o6YLFRHnk5QuHKk4= MIME-Version: 1.0 Received: by 10.68.4.72 with SMTP id i8mr9519039pbi.269.1311058949458; Tue, 19 Jul 2011 00:02:29 -0700 (PDT) Received: by 10.68.66.73 with HTTP; Tue, 19 Jul 2011 00:02:29 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Jul 2011 15:02:29 +0800 Message-ID: Subject: Re: how to restart a hbase cluster From: Weihua JIANG To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 It seems stop-hbase.sh only stops master/backup masters and zookeepers. So, according to my understanding, region servers shall shutdown itself since it can't find either master or zookeeper. But, I made a recent experimentation on our hbase cluster. After 2 days of mater/zookeeper shutdown, the region servers are still alive. I am not sure whether it is the problem in hbase release or our own problem since our version is a heavy patched one. Then, can I perform hbase cluster in following way? 1. stop master 2. stop master backups 3. stop zookeepers 4. stop region servers The only difference is step #4. If I manually stop down RS, will it affect data integrity? If not, then I can safely performed the steps to shutdown the cluster. Thanks Weihua 2011/7/13 Ted Yu : > For #2: > > bin/stop-hbase.sh > check that master and region servers are down > ... > bin/start-hbase.sh > > On Tue, Jul 12, 2011 at 11:29 PM, Weihua JIANG wrote: > >> Hi all, >> >> I am using HBase 0.90+HBASE-3789 and I want to know how to restart the >> cluster safely. >> >> Basically, there are two kinds of restarts: >> 1. Keep the HBase cluster working while restarting the whole cluster. >> 2. Stop-the-world cluster restart which only ensure data safety. >> >> From my understanding, graceful_stop.sh and rolling restart is used >> for kind #1. But, HBASE-3789 said it broke rolling restart. So, can >> anyone tell me what it broke and how to fix it to make rolling restart >> work? >> >> And, I can't find document about the kind #2 stop-the-world restart. >> Can any one point me the how-to document about it? >> >> Thanks >> Weihua >> >