Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7BA2920C for ; Fri, 17 Feb 2012 00:58:31 +0000 (UTC) Received: (qmail 45336 invoked by uid 500); 17 Feb 2012 00:58:31 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 45301 invoked by uid 500); 17 Feb 2012 00:58:31 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 45289 invoked by uid 99); 17 Feb 2012 00:58:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 00:58:31 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2012 00:58:29 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 427FB1BB888 for ; Fri, 17 Feb 2012 00:58:08 +0000 (UTC) Date: Fri, 17 Feb 2012 00:58:08 +0000 (UTC) From: "Jesse Yates (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <2139380032.49048.1329440288273.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <952564254.15765.1328725981536.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209944#comment-13209944 ] Jesse Yates commented on HBASE-5353: ------------------------------------ To follow up on Nicholas's comment, this would also be _just a configuration option_, not changing the way you have to run HBase. If it makes more sense for your setup to have a couple known masters that you monitor (the current impl), then you can do it that way. Alternatively, if you just want to have 1 daemon running for hbase - a region/masterServer - then you can do that too. A lot of the motivation around this jira was to try and make lives' easier by having less stuff to worry about. > 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(s) must be considered a 'special' node (though not a single point of failover), meaning that the node must be protected more than the other cluster machines or at least specially monitored. Minimally, we always need to ensure that the master is running, rather than letting the system handle that internally. It should be possible to instead have the HMaster be much more available, either in a distributed sense (meaning a bit rewrite) or multiple, dynamically created instances combined with the hot fail-over of masters. -- 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