[ https://issues.apache.org/jira/browse/HBASE-22905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921031#comment-16921031 ]
Hudson commented on HBASE-22905: -------------------------------- Results for branch branch-2.1 [build #1548 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1548/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (x) {color:red}-1 general checks{color} -- Something went wrong running this stage, please [check relevant console output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1548//console]. (x) {color:red}-1 jdk8 hadoop2 checks{color} -- Something went wrong running this stage, please [check relevant console output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1548//console]. (x) {color:red}-1 jdk8 hadoop3 checks{color} -- Something went wrong running this stage, please [check relevant console output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1548//console]. (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > Avoid temp ByteBuffer allocation in BlockingRpcConnection#writeRequest > ---------------------------------------------------------------------- > > Key: HBASE-22905 > URL: https://issues.apache.org/jira/browse/HBASE-22905 > Project: HBase > Issue Type: Improvement > Reporter: chenxu > Assignee: chenxu > Priority: Major > Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2 > > Attachments: HBASE-22905-master-v1.patch > > > Currently BlockingRpcConnection use ByteBufferOutputStream to serialize > CellBlock which involve temp ByteBuffer allocation, we can replace it with > netty’s ByteBufOutputStream, just like what > NettyRpcDuplexHandler#writeRequest doing -- This message was sent by Atlassian Jira (v8.3.2#803003)