hbase-issues mailing list archives

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

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

stack commented on HBASE-3833:

bq. 2. I would like to hear from folks regarding what they think of storing these files in
zk. Heck, why shouldn't we store the entire config in zk and the only config you need is the
address of the zk cluster?

Yeah, long time plan is to put all config. up in zk.  Would suggest though that that is out
of scope for this issue and that if your aim is to have this feature work like hadoop's, you
not move the includes/excludes there, at least, not as part of this issue.

Otherwise all else is good.  Good on you Vishal.

> 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