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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/08/30 00:28:07 UTC
[jira] [Commented] (YARN-60) NMs rejects all container tokens after
secret key rolls
[ https://issues.apache.org/jira/browse/YARN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444482#comment-13444482 ]
Vinod Kumar Vavilapalli commented on YARN-60:
---------------------------------------------
Independent discovery :) I started writing up tests for YARN-39 and immediately ran into this. Have a little patch, cleaning it up now. Will upload it soon.
> NMs rejects all container tokens after secret key rolls
> -------------------------------------------------------
>
> Key: YARN-60
> URL: https://issues.apache.org/jira/browse/YARN-60
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.2.0-alpha, 0.23.3
> Reporter: Daryn Sharp
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
>
> The NM's token secret manager will reject all container tokens after the secret key is activated which means the NM will not launch _any_ containers including AMs. The whole yarn cluster becomes inoperable in 1d.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira