[
https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HBASE-5353:
-------------------------------
Description: 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. (was: Currently, the HMaster node 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. 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. )
> 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
