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

stack resolved HBASE-22941.
---------------------------
    Fix Version/s: 2.2.2
                   2.1.7
                   2.3.0
                   3.0.0
     Hadoop Flags: Reviewed
       Resolution: Fixed

Thanks for the fix [~stoty] Took a while getting it in back to 2.1. Nice one.

> MetaTableAccessor.getMergeRegions() returns parent regions in random order
> --------------------------------------------------------------------------
>
>                 Key: HBASE-22941
>                 URL: https://issues.apache.org/jira/browse/HBASE-22941
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: master
>            Reporter: István Tóth
>            Assignee: István Tóth
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
>
> The multi-region merge patch has changed the behaviour of the 
> MetaTableAccessor.getMergeRegions() method. Earlier, the parent regions were 
> returned in the same order that they were passed to mergeRegion().
> The patch has changed this to return the regions in random order. To be more 
> precise, the parent regions are stored in random order in Meta.
> I propose storing and returning the parent regions in ascending order.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to