You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Haitian (Jira)" <ji...@apache.org> on 2024/11/14 02:13:00 UTC
[jira] [Resolved] (HADOOP-19316) Follow-up on ResourceManager quit due to ApplicationStateData exceeding znode limit
[ https://issues.apache.org/jira/browse/HADOOP-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Haitian resolved HADOOP-19316.
------------------------------
Resolution: Duplicate
> Follow-up on ResourceManager quit due to ApplicationStateData exceeding znode limit
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-19316
> URL: https://issues.apache.org/jira/browse/HADOOP-19316
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.3.6
> Reporter: Haitian
> Priority: Major
>
> In YARN-5006 the issue "ResourceManager quit due to ApplicationStateData exceeding znode limit" has been addressed , specifically in the storeApplicationStateInternal() method of the ZKRMStateStore class. However, the methods updateApplicationStateInternal(), storeApplicationAttemptStateInternal(), and updateApplicationAttemptStateInternal() also need to incorporate checks for the ZNode size limit in ZKRMStateStore class. This will help prevent scenarios where excessive data written to a single ZNode causes the ResourceManager (RM) and ZooKeeper (ZK) services to become unavailable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org