[
https://issues.apache.org/jira/browse/HBASE-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379357#comment-16379357
]
Hudson commented on HBASE-19989:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #361 (See
[https://builds.apache.org/job/HBase-1.3-IT/361/])
HBASE-19989 - READY_TO_MERGE and READY_TO_SPLIT do not update region (toffer:
rev d71042620b4d01b69197bbad51597e7990d9c545)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* (add)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestZKLessSplitOnCluster.java
* (add)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestZKLessMergeOnCluster.java
> READY_TO_MERGE and READY_TO_SPLIT do not update region state correctly
> ----------------------------------------------------------------------
>
> Key: HBASE-19989
> URL: https://issues.apache.org/jira/browse/HBASE-19989
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.1, 1.4.1
> Reporter: Ben Lau
> Assignee: Ben Lau
> Priority: Major
> Fix For: 1.3.2, 1.5.0, 1.4.3
>
> Attachments: HBASE-19989-branch-1.patch
>
>
> Region state transitions do not work correctly for READY_TO_MERGE/SPLIT.
> [~thiruvel] and I noticed this is due to break statements being in the wrong
> place in AssignmentManager. This allows a race condition for example in
> which one of the regions being merged could be moved concurrently, resulting
> in the merge transaction failing and then double assignment and/or dataloss.
> This bug appears to only affect branch-1 (for example 1.3 and 1.4) and not
> branch-2 as the relevant code in AM has since been rewritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
