[
https://issues.apache.org/jira/browse/HBASE-28010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758370#comment-17758370
]
Hudson commented on HBASE-28010:
--------------------------------
Results for branch branch-2
[build #868 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/868/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/868/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/868/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/868/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/868/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}
> Connection attributes can become corrupted on the server side
> -------------------------------------------------------------
>
> Key: HBASE-28010
> URL: https://issues.apache.org/jira/browse/HBASE-28010
> Project: HBase
> Issue Type: Bug
> Reporter: Bryan Beaudreault
> Assignee: Ray Mattingly
> Priority: Blocker
> Fix For: 2.6.0, 3.0.0-beta-1
>
>
> In ServerRpcConnection.processOneRpc, it calls processConnectionHeader and
> then immediately calls callCleanupIfNeeded. The parsing of the ByteBuff into
> the ConnectionHeader does not copy the bytes. We keep a reference to
> ConnectionHeader for later use, but since the underlying ByteBuff gets
> released in callCleanupIfNeeded, later requests can override the memory
> locations that the ConnectionHeader points at.
> The unit tests we added dont catch this possibly because they don't send
> enough requests to corrupt the buffers. It happens pretty quickly in a
> deployed cluster.
> We need to copy the List<NameBytesPair> from the ConnectionHeader into a Map
> before the buffer is released. This probably means we should remove
> getConnectionHeader from the RpcCall interface and instead add
> getConnectionAttributes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
