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

Hudson commented on HBASE-21921:
--------------------------------

Results for branch master
        [build #1168 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1168/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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
>         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
(v7.6.3#76005)

Reply via email to