[
https://issues.apache.org/jira/browse/YARN-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276466#comment-16276466
]
Arun Suresh commented on YARN-7522:
-----------------------------------
Thanks for working on this [~leftnoteasy].
Just thought of something: We are now assuming that tags are added only when
the RMContainer is allocated. That assumption might not really be true atleast
for the planning system. Assume our planning system is trying to distribute 3
container requests across 5 nodes (n1 - n5) with anti-affinity. Since the nodes
are initially not associated with any tags, the first container can be planned
on any node, but unless its RMContainer is allocated, the planning system won't
see which node has been tagged and will not be able to place the other 3
containers - unless the AM sends the requests separately. Essentially, we need
to simply be able to add/remove a tag to a node to allow the scheduler to keep
track
> Add application tags manager implementation
> -------------------------------------------
>
> Key: YARN-7522
> URL: https://issues.apache.org/jira/browse/YARN-7522
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-7522.YARN-6592.002.patch,
> YARN-7522.YARN-6592.003.patch, YARN-7522.YARN-6592.wip-001.patch
>
>
> This is different from YARN-6596, YARN-6596 is targeted to add constraint
> manager to store intra/inter application placement constraints. This JIRA is
> targeted to support storing maps between container-tags/applications and
> nodes. This will be required by affinity/anti-affinity implementation and
> cardinality.
--
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
