[
https://issues.apache.org/jira/browse/HBASE-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696300#comment-14696300
]
Hudson commented on HBASE-14000:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #616 (See
[https://builds.apache.org/job/HBase-1.1/616/])
HBASE-14000 Region server failed to report to Master and was stuck in
reportForDuty retry loop (Pankaj Kumar) (tedyu: rev
a2f82835953f17a9a2bee2b10c947d68990d2dd5)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
> Region server failed to report to Master and was 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
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.3
>
> Attachments: HBASE-14000.patch, HM_RS-Log_snippet.txt
>
>
> 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)
