You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2018/12/19 06:23:00 UTC
[jira] [Updated] (HBASE-21498) Master OOM when
SplitTableRegionProcedure new CacheConfig and instantiate a new BlockCache
[ https://issues.apache.org/jira/browse/HBASE-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guanghao Zhang updated HBASE-21498:
-----------------------------------
Issue Type: Bug (was: Improvement)
> Master OOM when SplitTableRegionProcedure new CacheConfig and instantiate a new BlockCache
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-21498
> URL: https://issues.apache.org/jira/browse/HBASE-21498
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.2, 2.0.4
>
> Attachments: HBASE-21498.master.001.patch, HBASE-21498.master.002.patch, HBASE-21498.master.003.patch, HBASE-21498.master.004.patch, HBASE-21498.master.005.patch, HBASE-21498.master.006.patch, HBASE-21498.master.006.patch, HBASE-21498.master.007.patch, HBASE-21498.master.007.patch
>
>
> In our cluster, we use a small heap/offheap config for master. After HBASE-21290, master doesn't instantiate BlockCache when it not carry table. But it will new CacheConfig in SplitTableRegionProcedure.splitStoreFiles method. And it will instantiate a new BlockCache if it not initialized before and make master OOM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)