hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers
Date Fri, 17 Feb 2012 00:58:08 GMT

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

Jesse Yates commented on HBASE-5353:

To follow up on Nicholas's comment, this would also be _just a configuration option_, not
changing the way you have to run HBase. If it makes more sense for your setup to have a couple
known masters that you monitor (the current impl), then you can do it that way. Alternatively,
if you just want to have 1 daemon running for hbase - a region/masterServer - then you can
do that too. A lot of the motivation around this jira was to try and make lives' easier by
having less stuff to worry about. 
> HA/Distributed HMaster via RegionServers
> ----------------------------------------
>                 Key: HBASE-5353
>                 URL: https://issues.apache.org/jira/browse/HBASE-5353
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.94.0
>            Reporter: Jesse Yates
>            Priority: Minor
> Currently, the HMaster node(s) must be considered a 'special' node (though not a single
point of failover), meaning that the node must be protected more than the other cluster machines
or at least specially monitored. Minimally, we always need to ensure that the master is running,
rather than letting the system handle that internally. It should be possible to instead have
the HMaster be much more available, either in a distributed sense (meaning a bit rewrite)
or multiple, dynamically created instances combined with the hot fail-over of masters. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message