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

Hudson commented on HBASE-27111:
--------------------------------

Results for branch branch-2.5
        [build #150 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/150/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/150/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/150/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/150/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/150/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


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


> Make Netty channel bytebuf allocator configurable
> -------------------------------------------------
>
>                 Key: HBASE-27111
>                 URL: https://issues.apache.org/jira/browse/HBASE-27111
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.5.0
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> Netty supports different strategies for allocating byte buffers for IO and 
> channel modules. We do not allow the site operator to fine tune this but 
> could. It would be particularly useful to allow preference of heap buffers 
> where direct memory may be limited or utilized for other purposes. 
> Support site configuration of the bytebuf allocator that Netty will use for 
> NettyRpcServer channels. Property name is 'hbase.netty.rpcserver.allocator'. 
> Default is no value, which is equivalent to "pooled". Valid values are:
> - "pooled": use PooledByteBufAllocator
> - "unpooled": use UnpooledByteBufAllocator
> - "heap": use HeapByteBufAllocator, which is a PooledByteBufAllocator that 
> preferentially allocates buffers on heap wherever possible
> - <class>: If the value is none of the recognized labels, treat it as a class 
> name implementing 
> org.apache.hbase.thirdparty.io.netty.buffer.ByteBufAllocator. This allows the 
> user to add a custom implementation, perhaps for debugging.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to