Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 29 Mar 2011 06:28:05 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <783120954.18276.1301380085650.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-3071) Graceful decommissioning of a
 regionserver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-3071:
-------------------------

    Attachment: 3071.txt

A graceful shutdown shell script and a ruby script that will move the regions off the regionserver one by one confirming region in new location before moving to the next.

> Graceful decommissioning of a regionserver
> ------------------------------------------
>
>                 Key: HBASE-3071
>                 URL: https://issues.apache.org/jira/browse/HBASE-3071
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>         Attachments: 3071.txt
>
>
> Currently if you stop a regionserver nicely, it'll put up its stopping flag and then close all hosted regions.  While the stopping flag is in place all region requests are rejected.  If this server was under load, closing could take a while.  Only after all is closed is the master informed and it'll restart assigning (in old master, master woud get a report with list of all regions closed, in new master the zk expired is triggered and we'll run shutdown handler).
> At least in new master, we have means of disabling balancer, and then moving the regions off the server one by one via HBaseAdmin methods -- we shoud write a script to do this at least for rolling restarts -- but we need something better.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira