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

Nick Dimiduk updated HBASE-28601:
---------------------------------
    Description: Specifying blockcache and memstore sizes as a percentage of 
heap is not always ideal. Sometimes it's easier to specify exact values rather 
than backing into a percentage. Let's introduce new configuration settings 
(perhaps named similarly to {{hbase.bucketcache.size}}) that accept byte 
values. Even nicer would be if these settings accepted human-friendly byte 
values like {{512m}} or {{10g}}.   (was: Specifying blockcache and memcache 
sizes as a percentage of heap is not always ideal. Sometimes it's easier to 
specify exact values rather than backing into a percentage. Let's introduce new 
configuration settings (perhaps named similarly to {{hbase.bucketcache.size}}) 
that accept byte values. Even nicer would be if these settings accepted 
human-friendly byte values like {{512m}} or {{10g}}. )
        Summary: Enable setting memstore on-heap sizes in bytes  (was: Enable 
setting memcache on-heap sizes in bytes)

Arg. I meant "memstore". Thanks for pointing it out, [~liuxiaocs7].

> Enable setting memstore on-heap sizes in bytes
> ----------------------------------------------
>
>                 Key: HBASE-28601
>                 URL: https://issues.apache.org/jira/browse/HBASE-28601
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> Specifying blockcache and memstore sizes as a percentage of heap is not 
> always ideal. Sometimes it's easier to specify exact values rather than 
> backing into a percentage. Let's introduce new configuration settings 
> (perhaps named similarly to {{hbase.bucketcache.size}}) that accept byte 
> values. Even nicer would be if these settings accepted human-friendly byte 
> values like {{512m}} or {{10g}}. 



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

Reply via email to