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 50F2310232 for ; Sun, 27 Oct 2013 05:01:40 +0000 (UTC) Received: (qmail 72979 invoked by uid 500); 27 Oct 2013 05:01:39 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 72790 invoked by uid 500); 27 Oct 2013 05:01:35 -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 72761 invoked by uid 99); 27 Oct 2013 05:01:32 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Oct 2013 05:01:32 +0000 Date: Sun, 27 Oct 2013 05:01:32 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9841) Provide tracking URL for cluster which is immune to master failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806223#comment-13806223 ] Ted Yu commented on HBASE-9841: ------------------------------- Here is the use case from Hoya point of view: When starting the HBase cluster, Hoya requests two containers for HMaster and multiple containers for region servers. It is unknown at time of request which nodes would host HMasters. After cluster starts running, the container for active master may go down. This would make the standby master active meanwhile YARN would start another container hosting HMaster to serve as the new standby master. It is desirable for HBase to provide an API which would tell Hoya about the location of the active master. Parsing the URL or decoding the server name from znode would work. But it is not straightforward. I was discussing with [~jmhsieh] at the meetup and he may be able to offer some idea. > Provide tracking URL for cluster which is immune to master failover > ------------------------------------------------------------------- > > Key: HBASE-9841 > URL: https://issues.apache.org/jira/browse/HBASE-9841 > Project: HBase > Issue Type: Task > Reporter: Ted Yu > > Currently each master provides web UI whose URL would not survive master failure. > For downstream project, it is desirable to have a tracking URL for the cluster which is always functional regardless which machine runs the active master. > One solution is to run light weight web server on designated server which serves the URL on well known port. -- This message was sent by Atlassian JIRA (v6.1#6144)