You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Moran (Jira)" <ji...@apache.org> on 2024/03/28 08:50:00 UTC

[jira] [Updated] (HBASE-7857) Sub-region management

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

Moran updated HBASE-7857:
-------------------------
    Description: 
Sub-region provides a light weight management below region level.
Matt Corgan has a nice summary of the relationship between region size and number of regions on region server:
https://issues.apache.org/jira/browse/HBASE-7667?focusedCommentId=13575024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13575024

HBASE-7667 proposed stripe compaction. However, to fully achieve fine-grained management, more components should participate:
 * memstore flush should ideally have knowledge about what makes stripe compaction work efficiently
 * we need to figure out where to store sub-region boundary information so that components have easy access. Boundary information should sustain after region moves from one server to another.

Since HBASE-7667 focuses on compaction aspect, this JIRA discusses sub-region management in other components so that we better understand the benefits and complexities.
 

  was:
Sub-region provides a light weight management below region level.
Matt Corgan has a nice summary of the relationship between region size and number of regions on region server:
https://issues.apache.org/jira/browse/HBASE-7667?focusedCommentId=13575024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13575024

HBASE-7667 proposed stripe compaction. However, to fully achieve fine-grained management, more components should participate:
* memstore flush should ideally have knowledge about what makes stripe compaction work efficiently
* we need to figure out where to store sub-region boundary information so that components have easy access. Boundary information should sustain after region moves from one server to another.

Since HBASE-7667 focuses on compaction aspect, this JIRA discusses sub-region management in other components so that we better understand the benefits and complexities.


> Sub-region management
> ---------------------
>
>                 Key: HBASE-7857
>                 URL: https://issues.apache.org/jira/browse/HBASE-7857
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Ted Yu
>            Priority: Major
>
> Sub-region provides a light weight management below region level.
> Matt Corgan has a nice summary of the relationship between region size and number of regions on region server:
> https://issues.apache.org/jira/browse/HBASE-7667?focusedCommentId=13575024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13575024
> HBASE-7667 proposed stripe compaction. However, to fully achieve fine-grained management, more components should participate:
>  * memstore flush should ideally have knowledge about what makes stripe compaction work efficiently
>  * we need to figure out where to store sub-region boundary information so that components have easy access. Boundary information should sustain after region moves from one server to another.
> Since HBASE-7667 focuses on compaction aspect, this JIRA discusses sub-region management in other components so that we better understand the benefits and complexities.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)