hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8635) Define prefetcher.resultsize.max as percentage
Date Thu, 30 May 2013 21:08:20 GMT

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

Jimmy Xiang commented on HBASE-8635:

Attached a patch. It changed the meaning of "hbase.hregionserver.prefetcher.resultsize.max"
from the actual bytes to the percentage.  Didn't change the parameter name. Added a check
to make sure the value is between 0 and 1.  The default is 0.1.  The max heap size is calculated
only once in HRegionServer to save some time, although it could change according to the java
> Define prefetcher.resultsize.max as percentage
> ----------------------------------------------
>                 Key: HBASE-8635
>                 URL: https://issues.apache.org/jira/browse/HBASE-8635
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-8635.patch
> Currently "hbase.hregionserver.prefetcher.resultsize.max" defines global limit for prefetching.
> The default value is 256MB.
> It would be more flexible to define this measure as a percentage of the heap.

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