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 "Weiwei Yang (JIRA)" <ji...@apache.org> on 2018/07/10 08:23:00 UTC
[jira] [Updated] (YARN-8511) When AM releases a container, RM
removes allocation tags before it is released by NM
[ https://issues.apache.org/jira/browse/YARN-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang updated YARN-8511:
------------------------------
Attachment: YARN-8511.001.patch
> When AM releases a container, RM removes allocation tags before it is released by NM
> ------------------------------------------------------------------------------------
>
> Key: YARN-8511
> URL: https://issues.apache.org/jira/browse/YARN-8511
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Affects Versions: 3.1.0
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Attachments: YARN-8511.001.patch
>
>
> User leverages PC with allocation tags to avoid port conflicts between apps, we found sometimes they still get port conflicts. This is a similar issue like YARN-4148. Because RM immediately removes allocation tags once AM#allocate asks to release a container, however container on NM has some delay until it actually gets killed and released the port. We should let RM remove allocation tags AFTER NM confirms the containers are released.
--
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