[jira] [Commented] (HBASE-27180) Multiple possible buffer leaks

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on HBASE-27180:
--------------------------------

Results for branch branch-2.5
	[build #160 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/160/]: (x) *{color:red}-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/160/General_20Nightly_20Build_20Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/160/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.5/160/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.5/160/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}


> Multiple possible buffer leaks
> ------------------------------
>
>                 Key: HBASE-27180
>                 URL: https://issues.apache.org/jira/browse/HBASE-27180
>             Project: HBase
>          Issue Type: Bug
>          Components: netty, regionserver
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-4, 2.4.14
>
>
> When using ByteBuf you need to be very careful about releasing it as otherwise you might leak data. There are various places in the code-base where such a leak could happen as the buffer is not correctly released



--
This message was sent by Atlassian Jira
(v8.20.10#820010)