Varun Saxena commented on YARN-2902:

[~djp], uploaded a patch backporting changes to branch-2.6
Changes in container-executor.c are not required as the change was necessitated 
by changes made in YARN-3089 which is not there in branch-2.6 
If YARN-3089 is ever brought into branch-2.6, it will break fix made by this 
JIRA(while using LCE).
Would a comment on that JIRA be enough to avoid this potential problem ?
However, YARN-3089 is unlikely to be backported to branch-2.6

We must backport YARN-4354(as you mentioned) and YARN-4380(the newly added test 
here fails intermittently without it) if we get this into branch-2.6

Also should I reopen this JIRA to run QA on this patch ?

> Killing a container that is localizing can orphan resources in the 
> ------------------------------------------------------------------------------------
>                 Key: YARN-2902
>                 URL: https://issues.apache.org/jira/browse/YARN-2902
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.5.0
>            Reporter: Jason Lowe
>            Assignee: Varun Saxena
>             Fix For: 2.7.2
>         Attachments: YARN-2902-branch-2.6.01.patch, YARN-2902.002.patch, 
> YARN-2902.03.patch, YARN-2902.04.patch, YARN-2902.05.patch, 
> YARN-2902.06.patch, YARN-2902.07.patch, YARN-2902.08.patch, 
> YARN-2902.09.patch, YARN-2902.10.patch, YARN-2902.11.patch, YARN-2902.patch
> If a container is in the process of localizing when it is stopped/killed then 
> resources are left in the DOWNLOADING state.  If no other container comes 
> along and requests these resources they linger around with no reference 
> counts but aren't cleaned up during normal cache cleanup scans since it will 
> never delete resources in the DOWNLOADING state even if their reference count 
> is zero.

This message was sent by Atlassian JIRA

Reply via email to