[
https://issues.apache.org/jira/browse/HBASE-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016236#comment-13016236
]
Hudson commented on HBASE-3071:
-------------------------------
Integrated in HBase-TRUNK #1831 (See
[https://hudson.apache.org/hudson/job/HBase-TRUNK/1831/])
> Graceful decommissioning of a regionserver
> ------------------------------------------
>
> Key: HBASE-3071
> URL: https://issues.apache.org/jira/browse/HBASE-3071
> Project: HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: stack
> Fix For: 0.92.0
>
> Attachments: 3071-v5.txt, 3071.txt, 3701-v2.txt, 3701-v3.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
