[
https://issues.apache.org/jira/browse/YARN-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541973#comment-16541973
]
Wangda Tan commented on YARN-8511:
----------------------------------
Thanks [~cheersyang], for explanation. I completely missed YARN-4148.
So for #1, it looks not a problem anymore.
#2 still exists, I think we can handle it separately.
Regarding to implementation, I saw the only purpose of changes added to RMNode
and subclasses is to access tags manager. Instead of doing this, is it better
to pass RMContext to SchedulerNode, so schedulerNode can directly access
RMContext like SchedulerAppAttempt?
> 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, YARN-8511.002.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: [email protected]
For additional commands, e-mail: [email protected]
