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 Wed, 04 May 2011 21:53:03 GMT

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

Vishal Kathuria commented on HBASE-3833:

stack: A quick question. I looked at region_mover.rb and I was wondering why this was implemented
in ruby as a script and not in the master. Since I do the parsing of the decom file in the
master, I would need to call out from master to the ruby script, which doesn't sound like
such a good idea. Secondly, if we improve the load balancing policy from just random to something
like load based, the ruby script would not be able to take advantage of it since random is
hard coded in it. 

Here is what I think we should ideally do:
1. Refactor the code in AssignmentManager/ServerShutdown handler to expose a function that
takes all the regions off a node.
2. Use the above function for decommissioning, failure handling and the unload admin commands
so we get similar behavior and single implementation across the three.

What do you guys think?

Agreed: I will leave the configs as is for this jira. I assume the config files need to live
on some NFS share so they are available when the master fails over - is that so?


> 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
> 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