[
https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684053#comment-13684053
]
Hadoop QA commented on YARN-693:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12587950/YARN-693-20130614.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.client.TestNMClient
org.apache.hadoop.yarn.client.TestAMRMClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1257//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/1257//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-api.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1257//console
This message is automatically generated.
> Sending NMToken to AM on allocate call
> --------------------------------------
>
> Key: YARN-693
> URL: https://issues.apache.org/jira/browse/YARN-693
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Omkar Vinit Joshi
> Assignee: Omkar Vinit Joshi
> Attachments: YARN-693-20130610.patch, YARN-693-20130613.patch,
> YARN-693-20130614.1.patch
>
>
> This is part of YARN-613.
> As per the updated design, AM will receive per NM, NMToken in following
> scenarios
> * AM is receiving first container on underlying NM.
> * AM is receiving container on underlying NM after either NM or RM rebooted.
> ** After RM reboot, as RM doesn't remember (persist) the information about
> keys issued per AM per NM, it will reissue tokens in case AM gets new
> container on underlying NM. However on NM side NM will still retain older
> token until it receives new token to support long running jobs (in work
> preserving environment).
> ** After NM reboot, RM will delete the token information corresponding to
> that AM for all AMs.
> * AM is receiving container on underlying NM after NMToken master key is
> rolled over on RM side.
> In all the cases if AM receives new NMToken then it is suppose to store it
> for future NM communication until it receives a new one.
> AMRMClient should expose these NMToken to client.
--
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
