You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bilwa S T (JIRA)" <ji...@apache.org> on 2019/01/24 10:21:00 UTC
[jira] [Commented] (YARN-9233) RM may report allocated container
which is killed (but not acquired by AM ) to AM which can cause spark AM
confused
[ https://issues.apache.org/jira/browse/YARN-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750977#comment-16750977 ]
Bilwa S T commented on YARN-9233:
---------------------------------
cc [~bibinchundatt] [~cheersyang]
> RM may report allocated container which is killed (but not acquired by AM ) to AM which can cause spark AM confused
> -------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-9233
> URL: https://issues.apache.org/jira/browse/YARN-9233
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bilwa S T
> Assignee: Bilwa S T
> Priority: Major
>
> After the RM kills an allocated (Allocated state) container for various reasons, it will go through the state transition process to the FINISHED state just like other state containers. Currently RM doesn't consider if container is acquired by the AM. Hence All the containers transitioned to FINISH state are added to justFinishedContainers list. Therefore the container that is not obtained by the AM and is killed by the rm will also return through the AM heartbeat. So AM re-applies for more resources than needed which would eventually cause number of containers to exceed the maximum limit
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org