[
https://issues.apache.org/jira/browse/HBASE-30038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076135#comment-18076135
]
Hudson commented on HBASE-30038:
--------------------------------
Results for branch branch-2.6
[build #37 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-2.6/37/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 client integration test for 2.10.2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop
client{color}
> RefCnt Leak error when caching
> ------------------------------
>
> Key: HBASE-30038
> URL: https://issues.apache.org/jira/browse/HBASE-30038
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-beta-1, 2.6.5
> Reporter: Dimas Shidqi Parikesit
> Assignee: Dimas Shidqi Parikesit
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0, 2.7.0, 2.6.6
>
>
> This bug is similar to
> [HBASE-28890|https://issues.apache.org/jira/browse/HBASE-28890]
> HFileBlock.Writer.getBlockForCaching() creates a ref-counted HFileBlock, and
> the caller must release its own reference after the cache has taken the
> ownership it needs.
> In HFileWriterImpl.java, the leak happened when shouldCacheBlock() returned
> before cacheFormatBlock.release() ran.
> In HFileBlockIndex.java, the intermediate-index path cached blockForCaching
> but never released the reference at all.
> Because these blocks can be backed by pooled off-heap ByteBuffs, repeated
> HFile writes could steadily drain allocator buffers and effectively leak
> memory, even though the blocks were only meant to live long enough to be
> considered for cache-on-write.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
