[
https://issues.apache.org/jira/browse/YARN-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113915#comment-16113915
]
Jian He commented on YARN-6920:
-------------------------------
So, the CONTAINER_COMPLETED event will first decrement the resource and the try
to start a container, it is possible that a different container gets started
later on SCHEDULE_CONTAINER event. I think we need to make sure the same
container gets started ?
Probably we can have a new event called RESTART_CONTAINER and
ContainerScheduler#handle can simply starts the container - skipping all those
dec/inc resource utilizations, checking opportunistic containers etc. And for
service container, user should be expected to always use Guaranteed type.
> 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: Arun Suresh
> Attachments: YARN-6920.001.patch, YARN-6920.002.patch,
> YARN-6920.003.patch, YARN-6920.004.patch
>
>
> 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
