[
https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203892#comment-13203892
]
Jesse Yates commented on HBASE-5353:
------------------------------------
{quote}
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).
{quote}
I worry about putting too much in the same jvm, especially when you ahve a
heavily loaded RS, you could be seriously killed with jvm pauses when you up
the size to accomodate the master (could be bad too when you have the larger
jvm, but no master running). Since, initially, this is going to be enabled via
a configuration option, another option would just be to start it in JVM vs.
outside the jvm; seems to me it would work either way.
{quote}
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.
{quote}
Talked wtih Lars H about doing this fix too - the client really doesn't need
the long running zk connection, but should just zk when it needs the master
info. So that could be part of this ticket too.
{quote}
Regards UI, we'd collapse it so that there'd be a single webapp rather than the
two we have now.
{quote}
Only works if we have same jvm stuff. I would argue that it should have a RS
link rather than a master link (smile). But for the initial patch I would say
the ui stuff should be on hold, until the actual implementation gets worked out.
> 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
