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

Hudson commented on YARN-3516:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #177 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/177/])
Update CHANGES.txt - Pulled in YARN-3465, YARN-3516, and YARN-3464 to 
branch-2.7 (for 2.7.1) (kasha: rev 32cd2c8d429ddb87348299c00b7d851246a25b4e)
* hadoop-yarn-project/CHANGES.txt


> killing ContainerLocalizer action doesn't take effect when private localizer 
> receives FETCH_FAILURE status.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3516
>                 URL: https://issues.apache.org/jira/browse/YARN-3516
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>            Priority: Minor
>             Fix For: 2.7.1
>
>         Attachments: YARN-3516.000.patch
>
>
> killing ContainerLocalizer action doesn't take effect when private localizer 
> receives FETCH_FAILURE status. This is a typo from YARN-3024. With YARN-3024, 
> ContainerLocalizer will be killed only if {{action}} is set to 
> {{LocalizerAction.DIE}}, calling {{response.setLocalizerAction}} will be 
> overwritten. This is also a regression from old code.
> Also it make sense to kill the ContainerLocalizer when FETCH_FAILURE 
> happened, because the container will send CLEANUP_CONTAINER_RESOURCES event 
> after localization failure.



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

Reply via email to