hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-7857) Sub-region management
Date Fri, 21 Jun 2013 04:27:19 GMT

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

stack resolved HBASE-7857.

    Resolution: Incomplete

Resolving speculative issue pulled from comments made in other issues w/ no fit criteria for
judging when this issue is done.
> Sub-region management
> ---------------------
>                 Key: HBASE-7857
>                 URL: https://issues.apache.org/jira/browse/HBASE-7857
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Ted Yu
> 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
> * 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message