hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishal Kathuria (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3833) ability to support includes/excludes list in Hbase
Date Tue, 24 May 2011 03:05:50 GMT

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

Vishal Kathuria commented on HBASE-3833:

My intention was build a graceful shutdown (that is the reason I assign the regions first
and then expire the server). I assumed that assign* API unloads them off the source region
server when assigning them to the new region server, but I guess I was wrong in that assumption.
Let me take a look at the code again to see how I can change it to make the shutdown graceful
and not have the situation you mentioned of two servers owning the region - that is clearly
not desirable.

In case any of the meta regions are involved, then the MetaServerShutdownHandler is dispatched.
That class has both  isCarryingRoot() and isCarryingMeta() defined.

I will publish another patch in a couple of days. Stack, please hold on to hacking this in.


> ability to support includes/excludes list in Hbase
> --------------------------------------------------
>                 Key: HBASE-3833
>                 URL: https://issues.apache.org/jira/browse/HBASE-3833
>             Project: HBase
>          Issue Type: Improvement
>          Components: client, regionserver
>    Affects Versions: 0.90.2
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: excl-patch.txt, excl-patch.txt
> An HBase cluster currently does not have the ability to specify that the master should
accept regionservers only from a specified list. This helps preventing administrative errors
where the same machine could be included in two clusters. It also allows the administrator
to easily remove un-ssh-able machines from the cluster.

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

View raw message