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

Hudson commented on YARN-3535:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #261 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/261/])
Pulling in YARN-3535 to branch 2.7.x (Arun Suresh: rev 
176131f12bc0d467e9caaa6a94b4ba96e09a4539)
* hadoop-yarn-project/CHANGES.txt


> Scheduler must re-request container resources when RMContainer transitions 
> from ALLOCATED to KILLED
> ---------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3535
>                 URL: https://issues.apache.org/jira/browse/YARN-3535
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler, fairscheduler, resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Peng Zhang
>            Assignee: Peng Zhang
>            Priority: Critical
>             Fix For: 2.7.2
>
>         Attachments: 0003-YARN-3535.patch, 0004-YARN-3535.patch, 
> 0005-YARN-3535.patch, 0006-YARN-3535.patch, YARN-3535-001.patch, 
> YARN-3535-002.patch, syslog.tgz, yarn-app.log
>
>
> During rolling update of NM, AM start of container on NM failed. 
> And then job hang there.
> Attach AM logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to