[
https://issues.apache.org/jira/browse/HBASE-23564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijin Bin updated HBASE-23564:
------------------------------
Description: TransitRegionStateProcedure (open a region on a server) may
run after the server have done ServerCrashProcedure. The ServerCrashProcedure
will remove the ServerName entry from serverMap in RegionStates, but later the
TransitRegionStateProcedure open a region on this server will add a entry in
serverMap in RegionStates for this ServerName, the open will fail and retry,
but serverMap in RegionStates leave some expired ServerNames and have no chance
to clear and make balance not correct. (was: TransitRegionStateProcedure (open
a region on a server) may run after the server have done ServerCrashProcedure.
The ServerCrashProcedure will remove the ServerName entry from serverMap in
RegionStates, but later the TransitRegionStateProcedure open a region on this
server will add a entry in serverMap in RegionStates for this ServerName, the
open will fail and retry, but serverMap in RegionStates has some expired
ServerNames and have no chance to clear and make balance not correct.)
> RegionStates may has some expired serverinfo and make regions do not balance.
> ------------------------------------------------------------------------------
>
> Key: HBASE-23564
> URL: https://issues.apache.org/jira/browse/HBASE-23564
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.2.2
> Reporter: Lijin Bin
> Assignee: Lijin Bin
> Priority: Major
>
> TransitRegionStateProcedure (open a region on a server) may run after the
> server have done ServerCrashProcedure. The ServerCrashProcedure will remove
> the ServerName entry from serverMap in RegionStates, but later the
> TransitRegionStateProcedure open a region on this server will add a entry in
> serverMap in RegionStates for this ServerName, the open will fail and retry,
> but serverMap in RegionStates leave some expired ServerNames and have no
> chance to clear and make balance not correct.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)