You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/01/23 17:53:00 UTC

[jira] [Updated] (HBASE-21921) Notify users if the ByteBufAllocator is always allocating ByteBuffers from heap which means the increacing GC pressure

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

Nick Dimiduk updated HBASE-21921:
---------------------------------
    Fix Version/s: 2.3.0
                   3.0.0

> Notify users if the ByteBufAllocator is always allocating ByteBuffers from heap which means the increacing GC pressure
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21921
>                 URL: https://issues.apache.org/jira/browse/HBASE-21921
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Minor
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: HBASE-21921.HBASE-21879.v01.patch, HBASE-21921.HBASE-21879.v02.patch, HBASE-21921.HBASE-21879.v03.patch, jmx-metrics.png, web-ui.png
>
>
> As the javadoc of ByteBuffAllocator says: 
> {code}
> There's possible that the desired memory size is large than ByteBufferPool has, we'll downgrade to allocate ByteBuffers from heap which meaning the GC pressure may increase again. Of course, an better way is increasing the ByteBufferPool size if we detected this case. 
> {code}
> So I think we need some messages to remind the user that an larger ByteBufferPool size may be better if the allocator allocate ByteBuffer from heap frequently. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)