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/08/10 12:32:01 UTC

[jira] [Created] (YARN-6982) Potential issue on setting AMContainerSpec#tokenConf to null before app is completed

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

             Summary: Potential issue on setting AMContainerSpec#tokenConf to null before app is completed
                 Key: YARN-6982
                 URL: https://issues.apache.org/jira/browse/YARN-6982
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Rohith Sharma K S


While reviewing patch for YARN-65, I found that many places RMAppImpl#submissionContext sets containerLaunchcontext#setTokensConf has been set to null i.e 
{code}
// set the memory free
app.submissionContext.getAMContainerSpec().setTokensConf(null);
{code}

This appears be a issue if application is updated may be because queue move or lifetime or priority, then submission context will be restored again into state store. Consider after app update, if RM is restarted then submission context will have null tokenConf. This could be a potential issue. 



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