Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 7 Aug 2016 16:05:20 +0000 (UTC)
From: "Heng Chen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12995430.1470475228000.243957.1470585920572@Atlassian.JIRA>
In-Reply-To: <JIRA.12995430.1470475228000@Atlassian.JIRA>
References: <JIRA.12995430.1470475228000@Atlassian.JIRA> <JIRA.12995430.1470475228896@arcas>
Subject: [jira] [Commented] (HBASE-16367) Race between master and region
 server initialization may lead to premature server abort
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 07 Aug 2016 16:05:23 -0000


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

Heng Chen commented on HBASE-16367:
-----------------------------------

+1

> Race between master and region server initialization may lead to premature server abort
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-16367
>                 URL: https://issues.apache.org/jira/browse/HBASE-16367
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 16367.v1.txt, 16367.v2.txt, 16367.v3.txt, 63908-master.log
>
>
> I was troubleshooting a case where hbase (1.1.2) master always dies shortly after start - see attached master log snippet.
> It turned out that master initialization thread was racing with HRegionServer#preRegistrationInitialization() (initializeZooKeeper, actually) since HMaster extends HRegionServer.
> Through additional logging in master:
> {code}
>     this.oldLogDir = createInitialFileSystemLayout();
>     HFileSystem.addLocationsOrderInterceptor(conf);
>     LOG.info("creating splitLogManager");
> {code}
> I found that execution didn't reach the last log line before region server declared cluster Id being null.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)