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

Hudson commented on HBASE-21508:
--------------------------------

Results for branch master
        [build #629 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/629/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/629//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/629//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/629//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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-v1.patch, HBASE-21508-v2.patch, 
> HBASE-21508-v3.patch, HBASE-21508-v3.patch, HBASE-21508-v4.patch, 
> 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)

Reply via email to