[
https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203872#comment-13203872
]
stack commented on HBASE-5353:
------------------------------
I'd say just run the master in-process w/ the regionserver. Master doesn't do
much (It used to be heavily loaded when we did log splitting but thats
distributed now or on startup... but even then, should be fine).
Client already tracks master location as you say though we need to undo
this...and just have the client do a read of zk to find master location when it
needs it.
Regards UI, we'd collapse it so that there'd be a single webapp rather than the
two we have now. There'd be a 'master' link. If the current regionserver were
not the master, the master link would redirect you to current master.
> 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
