[
https://issues.apache.org/jira/browse/YARN-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304026#comment-16304026
]
Panagiotis Garefalakis commented on YARN-7682:
----------------------------------------------
Thanks for the comments [~asuresh] and [~kkaranasos]!
bq. If we want to make the canAssign be part of the PCM, I think we should make
the tags manager be a field of the PCM rather than passing it as a parameter
(i.e., pass the tag manager during PCM's initialization
Make sense to me
bq. We can support composite constraints as a second step (including delayed
or).
Sure, working on an updated version with Simple constraints now.
bq. What about rack scope, given YARN-7653 is there
Agree, changing the API accordingly for the new patch
> Expose canAssign method in the PlacementConstraintManager
> ---------------------------------------------------------
>
> Key: YARN-7682
> URL: https://issues.apache.org/jira/browse/YARN-7682
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Panagiotis Garefalakis
> Attachments: YARN-7682.wip.patch
>
>
> As per discussion in YARN-7613. Lets expose {{canAssign}} method in the
> PlacementConstraintManager that takes a sourceTags, applicationId,
> SchedulerNode and AllocationTagsManager and returns true if constraints are
> not violated by placing the container on the node.
> I prefer not passing in the SchedulingRequest, since it can have > 1
> numAllocations. We want this api to be called for single allocations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
