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 2nd secret key roll
Date Wed, 29 Aug 2012 18:30:10 GMT

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

Daryn Sharp commented on YARN-60:

We had another cluster break after 24h, before the new key should have been activated.  I
didn't see anything interesting in the logs, but I'll look again.
> NMs rejects all container tokens after 2nd secret key roll
> ----------------------------------------------------------
>                 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 third secret
key is activated which means the NM will not launch _any_ containers including AMs.  The whole
yarn cluster becomes inoperable in 2d 15m (default 1d key roll + 15m activation delay).
> The NM tracks the previous 2 secrets, so either the RM is generating tokens with an old
secret, or more likely the NMs are going out of sync when discarding the oldest secret.

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