[jira] [Commented] (HBASE-3071) Graceful decommissioning of a regionserver

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012640#comment-13012640 ] 

Jean-Daniel Cryans commented on HBASE-3071:
-------------------------------------------

Typo in "minus the ond to decommission"

Don't create two new HTable per region moved in move(), it's gonna get expensive very soon.

When trying to get the first row, you could just use the FirstKeyOnlyFilter and even the KeyOnlyFilter.

The "Moving" message is weird, it's not clear it's iterating starting from 0.

Could admin.move fail and abort the whole process if the region has split?

> 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