hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14000) Region server failed to report Master and stuck in reportForDuty retry loop
Date Wed, 08 Jul 2015 17:25:06 GMT

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

Jerry He commented on HBASE-14000:

bq. but by the time master (HM1) finish initialization another master (HM2) became active.
When HM1 is initializing, it would continue to hold onto the master znode on ZK. HM2 can not
become active master.  Unless there is bug somewhere in there.
Can you paste the HM1, HM2 and the region sever logs around the time of the master failover?

> 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

This message was sent by Atlassian JIRA

View raw message