[
https://issues.apache.org/jira/browse/YARN-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110009#comment-16110009
]
Arun Suresh commented on YARN-6920:
-----------------------------------
Actually, let me take over this [~haibochen], if you don't mind.
On further investigation, it looks like the actual issue is due to the fact
that during container re-initialization, the container resources which should
have been reclaimed by the ContainerScheduler before re-launching the
re-initialized container, was never re-claimed - which resulted in a resource
leak.
This was not happening earlier either, but due to the fact that prior to
YARN-6706, if maxOppQueueLength == 0, we never even used to perform a resource
availability check, the ContainerManager test-cases used to pass :)
Will post the fix shortly along with some additional assertions.
> fix TestNMClient failure due to YARN-6706
> -----------------------------------------
>
> Key: YARN-6920
> URL: https://issues.apache.org/jira/browse/YARN-6920
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Haibo Chen
>
> Looks like {{TestNMClient}} has been failing for a while. Opening this JIRA
> to track the fix.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
