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

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/07/14 18:27:00 UTC

[jira] [Updated] (HBASE-24256) When fixOverlap hits the max region limit, it is possible to include the same region in multiple merge request

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

Nick Dimiduk updated HBASE-24256:
---------------------------------
        Fix Version/s:     (was: 2.4.0)
    Affects Version/s:     (was: 2.4.0)

> When fixOverlap hits the max region limit, it is possible to include the same region in multiple merge request
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-24256
>                 URL: https://issues.apache.org/jira/browse/HBASE-24256
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck2
>    Affects Versions: 3.0.0-alpha-1, 2.3.0
>            Reporter: Huaxiang Sun
>            Assignee: Huaxiang Sun
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> If the same region is included in multiple merge requests, the first merge cleans up the region state, the second merge request will fail with error msg "No state for region ****". The algo needs to be improved to make sure the same region is not included in multi merge requests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)