You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 01:36:00 UTC

[jira] [Resolved] (HBASE-7877) KeyPrefixRegionSplitPolicy and DelimitedKeyPrefixRegionSplitPolicy splits are not always optimal

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

Andrew Kyle Purtell resolved HBASE-7877.
----------------------------------------
    Resolution: Incomplete

> KeyPrefixRegionSplitPolicy and DelimitedKeyPrefixRegionSplitPolicy splits are not always optimal
> ------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7877
>                 URL: https://issues.apache.org/jira/browse/HBASE-7877
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.94.5, 0.95.2
>            Reporter: Robert Dyer
>            Priority: Minor
>
> With KeyPrefixRegionSplitPolicy (and now DelimitedKeyPrefixRegionSplitPolicy), if a split would break a group of keys it is modified to become the first key in the group's range.  This is not always optimal.  If the distribution of keys are such that the group containing the split has half the keys in the region, then no split will occur.
> The best solution would be to compute both the current key group's first key (what the current implementation does) as well as the next key group's first key and then choosing which of the two is closest to the original split point.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)