You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "HBase Review Board (JIRA)" <ji...@apache.org> on 2010/07/17 03:06:51 UTC

[jira] Commented: (HBASE-2844) Capping the number of regions

    [ https://issues.apache.org/jira/browse/HBASE-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889442#action_12889442 ] 

HBase Review Board commented on HBASE-2844:
-------------------------------------------

Message from: "Pranav Khaitan" <pr...@facebook.com>

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/334/
-----------------------------------------------------------

Review request for hbase, Jonathan Gray, Karthik Ranganathan, and Kannan Muthukkaruppan.


Summary
-------

This patch is for capping the number of regions on a region server depending on different use-cases. We add a parameter in the config file which can be used by the user to set this value. The default value is INT_MAX. 


This addresses bug HBASE-2844.
    http://issues.apache.org/jira/browse/HBASE-2844


Diffs
-----

  trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java 964968 
  trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 964968 
  trunk/src/main/resources/hbase-default.xml 964968 
  trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServer.java PRE-CREATION 

Diff: http://review.hbase.org/r/334/diff


Testing
-------

Existing tests passing. Written more specialized tests at HRegionServer level


Thanks,

Pranav




> Capping the number of regions
> -----------------------------
>
>                 Key: HBASE-2844
>                 URL: https://issues.apache.org/jira/browse/HBASE-2844
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Pranav Khaitan
>            Assignee: Pranav Khaitan
>            Priority: Minor
>
> It may sometimes be advantageous to prevent the number of regions from growing very large. This may happen if the values are large in size even though the number of keyvalues are not large. If the number of regions becomes too large, then it is difficult to accommodate the memstore for each region in memory. In such cases, we either have to flush out memstore to disk or decrease size of each memstore.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.