[
https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204048#comment-13204048
]
Todd Lipcon commented on HBASE-5353:
------------------------------------
bq. But this means you don't need to worry about where you run your master
Except it opens a new can of worms: where do you find the master UI? how do you
monitor your master if it moves around? how do you easily find the master logs
when it could be anywhere in the cluster?
If your goal is to automatically pick a system to run a master on, you could
have your cluster management software do that, but I only see additional
complexity being introduced if you add this to HBase proper.
> 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 must be considered a 'special' node (single point
> of failure), meaning that the node must be protected more than the other
> commodity machines. It should be possible to instead have the HMaster be much
> more available, either in a distributed sense (meaning a bit rewrite) or with
> multiple instances and automatic failover.
--
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
