Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 1 Sep 2012 06:23:07 +1100 (NCT)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <1581740935.24296.1346440987937.JavaMail.jiratomcat@arcas>
In-Reply-To: <218805250.12762.1346262369070.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (YARN-60) NMs rejects all container tokens after
 secret key rolls
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans commented on YARN-60:
-----------------------------------------

Looks like you already checked it in.  I can take care of checking in the fix.
                
> 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