[
https://issues.apache.org/jira/browse/HBASE-25032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342905#comment-17342905
]
Nick Dimiduk commented on HBASE-25032:
--------------------------------------
bq. Oops, this patch was committed on 25th March and 2.3.5RC1 came out on 26th
March, so I got confused and ended up adding the wrong release version. Is
there is a better way to avoid this race rather than keeping track of emails in
dev@?
Tracking the content of the CHANGES.md file is one way. Another way is to check
the git history of the branch for a commit's place in relation to the release
tags. Either way, a release manager usually cleans up these kinds of
inconsistencies as they prepare the next patch release, so it would have been
caught as part of preparation for 2.3.6RC0.
> Wait for region server to become online before adding it to online servers in
> Master
> ------------------------------------------------------------------------------------
>
> Key: HBASE-25032
> URL: https://issues.apache.org/jira/browse/HBASE-25032
> Project: HBase
> Issue Type: Bug
> Reporter: Sandeep Guggilam
> Assignee: Caroline Zhou
> Priority: Major
> Labels: master, regionserver
> Fix For: 3.0.0-alpha-1, 2.5.0
>
>
> As part of RS start up, RS reports for duty to Master . Master acknowledges
> the request and adds it to the onlineServers list for further assigning any
> regions to the RS
> Once Master acknowledges the reportForDuty and sends back the response, RS
> does a bunch of stuff like initializing replication sources etc before
> becoming online. However, sometimes there could be an issue with initializing
> replication sources when it is unable to connect to peer clusters because of
> some kerberos configuration and there would be a delay of around 20 mins in
> becoming online.
>
> Since master considers it online, it tries to assign regions and which fails
> with ServerNotRunningYet exception, then the master tries to unassign which
> again fails with the same exception leading the region to FAILED_CLOSE state.
>
> It would be good to have a check to see if the RS is ready to accept the
> assignment requests before adding it to online servers list which would
> account for any such delays as described above
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
