You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/11/24 07:05:00 UTC
[jira] [Updated] (HBASE-21508) Ignore the
reportRegionStateTransition call from a dead server
[ https://issues.apache.org/jira/browse/HBASE-21508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-21508:
------------------------------
Assignee: Duo Zhang
Status: Patch Available (was: Open)
> Ignore the reportRegionStateTransition call from a dead server
> --------------------------------------------------------------
>
> Key: HBASE-21508
> URL: https://issues.apache.org/jira/browse/HBASE-21508
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21508.patch
>
>
> In our ITBLL test we observer a race between the SCP and TRSP which causes a region being assigned to two region servers.
> Not fully understand the scenario, but anyway, the we do not consider the situation in the old code, that after SCP gets the region list of a dead server, there could still be a reportRegionStateTransition call from dead server and mess up things.
> In general, I think we should have a fence in the AssignmentManager to prevent the reportRegionStateTransition from the dead servers to mess up the states.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)