Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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.

        Issue Links

          Activity

          stack made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Incomplete [ 4 ]
          Sergey Shelukhin made changes -
          Link This issue is related to HBASE-7630 [ HBASE-7630 ]
          Ted Yu made changes -
          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.

          User may want to see how sub-regions are shaped on web UI.
          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.
          Ted Yu made changes -
          Link This issue relates to HBASE-7667 [ HBASE-7667 ]
          Ted Yu made changes -
          Issue Type Bug [ 1 ] New Feature [ 2 ]
          Ted Yu made changes -
          Field Original Value New Value
          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

          Since HBASE-7667 focuses on compaction aspect, this JIRA discusses sub-region management in other components.

          User may want to see how sub-regions are shaped on web UI.
          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.

          User may want to see how sub-regions are shaped on web UI.
          Ted Yu created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Ted Yu
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development