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

Jim Brennan commented on YARN-8672:
-----------------------------------

patch 003 fixes 2 of the three checkstyle issues.  The last one is:
{noformat}
./hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/ContainerLocalizer.java:409:
  public static void buildMainArgs(List<String> command,:22: More than 7 
parameters (found 8). {noformat}
This matches the trunk version.

> TestContainerManager#testLocalingResourceWhileContainerRunning occasionally 
> times out
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-8672
>                 URL: https://issues.apache.org/jira/browse/YARN-8672
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.10.0, 3.2.0
>            Reporter: Jason Darrell Lowe
>            Assignee: Chandni Singh
>            Priority: Major
>             Fix For: 3.3.0
>
>         Attachments: YARN-8672-branch-2.10.001.patch, 
> YARN-8672-branch-2.10.002.patch, YARN-8672-branch-2.10.003.patch, 
> YARN-8672.001.patch, YARN-8672.002.patch, YARN-8672.003.patch, 
> YARN-8672.004.patch, YARN-8672.005.patch, YARN-8672.006.patch, 
> YARN-8672.007.patch, YARN-8672.008.patch
>
>
> Precommit builds have been failing in 
> TestContainerManager#testLocalingResourceWhileContainerRunning.  I have been 
> able to reproduce the problem without any patch applied if I run the test 
> enough times.  It looks like something is removing container tokens from the 
> nmPrivate area just as a new localizer starts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to