You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 20:01:01 UTC

[jira] [Updated] (HBASE-19989) READY_TO_MERGE and READY_TO_SPLIT do not update region state correctly

     [ https://issues.apache.org/jira/browse/HBASE-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-19989:
-----------------------------------
    Fix Version/s:     (was: 1.5.0)

> 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.4.3
>
>         Attachments: HBASE-19989-ADDENDUM-branch-1.patch, 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)