[
https://issues.apache.org/jira/browse/HBASE-22185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814208#comment-16814208
]
Hudson commented on HBASE-22185:
--------------------------------
Results for branch branch-2.2
[build #170 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/170/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/170//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/branch-2.2/170//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/branch-2.2/170//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> RAMQueueEntry#writeToCache should freeBlock if any exception encountered
> instead of the IOException catch block
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22185
> URL: https://issues.apache.org/jira/browse/HBASE-22185
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.0.6, 1.5.1, 2.1.5
>
>
> When preparing patch for HBASE-22159, I found that if thrown an
> AssertionError in RAMQueueEntry#writeToCache, the bucketAllocator won't free
> its memory.
> This is an memory leak bug, and should be fixed in almost all 2.x branches.
> will also check branch-1.x
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
