[
https://issues.apache.org/jira/browse/YARN-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822960#comment-16822960
]
Xianghao Lu commented on YARN-6825:
-----------------------------------
[~Feng Yuan]
as what [~bibinchundatt] said， applicationUpdate can be handled by configuring
less value
attemptAdd, attemptUpdate can be handled by YARN-6125, YARN-6967
more details for zk data size limit in yarn, please refer to YARN-9498
> RM quit due to ApplicationStateData exceed the limit size of znode in zk
> ------------------------------------------------------------------------
>
> Key: YARN-6825
> URL: https://issues.apache.org/jira/browse/YARN-6825
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Rohith Sharma K S
> Priority: Major
>
> YARN-5006 fixes this issue by strict validation for ApplicationStateData
> length against 1MB(default max jute buffer) during application submission
> only. There is possibility of thrashing as dead zone was not properly
> defined/taken care.
> But it do not consider scenarios where ApplicationStateData can be increased
> later point of time i.e
> # If app is submitted with less than 1MB during submission, later updated
> like queue name or life time value or priority is changed. The app update
> call will be sent to statestore which cause same issue because
> ApplicationStateData length has increased.
> # Consider there is no app update, but final state are stored in ZK. This
> adds up several fields such finishTime, finalState, finalApplicationState.
> This increases size of ApplicationStateData.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
