Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 7 Jul 2015 10:31:04 +0000 (UTC)
From: "Pankaj Kumar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12841680.1435667806000.116084.1436265064855@Atlassian.JIRA>
In-Reply-To: <JIRA.12841680.1435667806000@Atlassian.JIRA>
References: <JIRA.12841680.1435667806000@Atlassian.JIRA>
 <JIRA.12841680.1435667806073@arcas>
Subject: [jira] [Commented] (HBASE-14000) Region server failed to report
 Master and stuck in reportForDuty retry loop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pankaj Kumar commented on HBASE-14000:
--------------------------------------

[~tedyu], I tried but I am not able to simulate this scenario in test case.

> Region server failed to report Master and stuck in reportForDuty retry loop
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-14000
>                 URL: https://issues.apache.org/jira/browse/HBASE-14000
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Pankaj Kumar
>            Assignee: Pankaj Kumar
>         Attachments: HBASE-14000.patch
>
>
> In a HA cluster, region server got stuck in reportForDuty retry loop if the active master is restarting and later on master switch happens before it reports successfully.
> Root cause is same as HBASE-13317, but the region server tried to connect master when it was starting, so rssStub reset didnt happen as
> {code}
>   if (ioe instanceof ServerNotRunningYetException) {
> 	LOG.debug("Master is not running yet");
>   }
> {code}
> When master starts, master switch happened. So RS always tried to connect to standby master.


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