You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2017/07/14 09:04:01 UTC

[jira] [Created] (YARN-6825) RM quit due to ApplicationStateData exceed the limit size of znode in zk

Rohith Sharma K S created YARN-6825:
---------------------------------------

             Summary: 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


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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org