hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-60) NMs rejects all container tokens after secret key rolls
Date Thu, 30 Aug 2012 13:41:08 GMT

    [ https://issues.apache.org/jira/browse/YARN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444952#comment-13444952

Daryn Sharp commented on YARN-60:

This seems to make spurious (albeit generally good) changes.  Has the patch removed the ability
to easily add per-node secret keys?  If true, could the patch be much simpler if that functionality
is left intact?
> 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
>         Attachments: YARN-60-20120829.1.txt, YARN-60-20120829.2.txt, YARN-60-20120829.txt
> 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

View raw message