You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ShuangQi Xia (Jira)" <ji...@apache.org> on 2021/07/23 11:09:00 UTC
[jira] [Updated] (HBASE-26116) Parallel scheduling of
getClusterstatus interface will lead to linear growth of HMaster memory
[ https://issues.apache.org/jira/browse/HBASE-26116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ShuangQi Xia updated HBASE-26116:
---------------------------------
Summary: Parallel scheduling of getClusterstatus interface will lead to linear growth of HMaster memory (was: Parallel scheduling of getClusterstatus interface will lead to linear growth of hmaster memory)
> Parallel scheduling of getClusterstatus interface will lead to linear growth of HMaster memory
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-26116
> URL: https://issues.apache.org/jira/browse/HBASE-26116
> Project: HBase
> Issue Type: Bug
> Components: mapreduce, master
> Affects Versions: 1.3.1, 2.2.3
> Reporter: ShuangQi Xia
> Priority: Major
>
> when Mapreduce job and Spark job use TableInputFormat.getSplits will call getclusterstatus ,and when running more ten job, HMaster memory is very high，Of course, the region quantity itself is a reason
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)