Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 17 Apr 2017 16:39:41 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13063229.1491924940000.297498.1492447181778@Atlassian.JIRA>
In-Reply-To: <JIRA.13063229.1491924940000@Atlassian.JIRA>
References: <JIRA.13063229.1491924940000@Atlassian.JIRA> <JIRA.13063229.1491924940186@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-17902) Backport HBASE-16367 "Race between
 master and region server initialization may lead to premature server abort"
 to 1.3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Apr 2017 16:39:46 -0000


     [ https://issues.apache.org/jira/browse/HBASE-17902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-17902:
---------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

> Backport HBASE-16367 "Race between master and region server initialization may lead to premature server abort" to 1.3
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17902
>                 URL: https://issues.apache.org/jira/browse/HBASE-17902
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 1.3.2
>
>         Attachments: 17902.branch-1.3.txt
>
>
> This is to fix the case where hbase master always dies shortly after start.
> 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.
> branch-1.3 has been in quiet mode leading up to the release of 1.3.1
> Once 1.3.1 is released, the fix can go into branch-1.3


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)