[
https://issues.apache.org/jira/browse/HBASE-22929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929124#comment-16929124
]
Hudson commented on HBASE-22929:
--------------------------------
Results for branch branch-2.2
[build #603 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/603/]:
(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/603//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/603//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/603//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> MemStoreLAB ChunkCreator may memory leak
> -----------------------------------------
>
> Key: HBASE-22929
> URL: https://issues.apache.org/jira/browse/HBASE-22929
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.1.2
> Reporter: Yechao Chen
> Assignee: ramkrishna.s.vasudevan
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
> Attachments: OOM_log.png, hbase-site.xml, hbase_heap_monitor.png,
> hbase_rs_heap_dump_mat_1.png,
> hbase_rs_heap_dump_mat_ChunkCreator_chunkIdMap.png, hbase_rs_mem_used.png
>
>
> We use hbase 2.1.2 with memstorelab enable
> RegionServer crashed case of oom
> I dump the heap ,found the ChunkCreator may be memory leak
> The heap is 32GB,
> hbase.regionserver.global.memstore.size=0.4,
> hbase.hregion.memstore.mslab.enabled=true
> hbase.hregion.memstore.chunkpool.initialsize=0.5,
> hbase.hregion.memstore.chunkpool.maxsize=1.0
> BucketCache with offheap
--
This message was sent by Atlassian Jira
(v8.3.2#803003)