[
https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204123#comment-13204123
]
Todd Lipcon commented on HBASE-5353:
------------------------------------
bq. We have the above (mostly unsolved) problems now if you run with more than
one master.
bq. They should be doing this now, if multiple masters?
Sort of - except when you have two masters, you just set up nagios alerts and
metrics to point to both, and you only need to look two places if you have an
issue. If you have no idea where the master is, you have to hunt around the
cluster to find it.
bq. If the master function were lightweight enough, it'd be kinda sweet having
one daemon type only I'd think
Except we'd still have multiple daemon types, logically, it's just that they'd
be collocated inside the same process, making logs harder to de-interleave, etc.
Plus, if your RS are are all collocated with TTs and heavily loaded, then I
wouldn't want to see the master running on one of them. I'd rather just tell
ops "these nodes run the important master daemons, please monitor them and any
high utilization is problematic".
> 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
