hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers
Date Wed, 08 Feb 2012 23:34:57 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204113#comment-13204113
] 

stack commented on HBASE-5353:
------------------------------

bq. 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?

Its not a new can of worms, right?  We have the above (mostly unsolved) problems now if you
run with more than one master.

bq. And any cron jobs or nagios alerts you write need to first call some HBase utility to
find the active master's IP via ZK in order to get to it?

They should be doing this now, if multiple masters?

If the master function were lightweight enough, it'd be kinda sweet having one daemon type
only I'd think; there'd be no longer need for special treatment of master.  Might be tricky
having them running in the same JVM what w/ all the executors afloat and RPCs (I'd rather
do all in the one JVM then have RS start/stop separate Master processes if we were going to
go this route).
                
> 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

        

Mime
View raw message