[
https://issues.apache.org/jira/browse/YARN-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303343#comment-16303343
]
Arun Suresh commented on YARN-7613:
-----------------------------------
bq. in a previous draft patch I had the method as part of the constraint
manager for example which did make some sense.
Yeah, that's probably a good idea - since the PCM is available to the scheduler
anyway (while the algorithm is not). We can just call:
{code}
public boolean attemptAllocationOnNode(SchedulerApplicationAttempt appAttempt,
SchedulingRequest schedulingRequest, SchedulerNode schedulerNode) {
...
PlacementConstraintManager pcm = ...
AllocationTagsManager tm = ...
if (!pcm.canAssign(appAttempt.getApplicationId(), schedulingRequest,
schedulerNode, tm))) {
return false;
}
...
{code}
w.r.t the AlgorithmContext
Yeah, that should still be something only the Dispatcher and Algorithm
interacts with - an argument to the place() method. Lets keep that out of the
Scheduler phase.
We should have the canAssign change as its own JIRA and have YARN-7681 and this
depend on it.
> Implement Planning algorithms for rich placement
> ------------------------------------------------
>
> Key: YARN-7613
> URL: https://issues.apache.org/jira/browse/YARN-7613
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Panagiotis Garefalakis
> Attachments: YARN-7613.wip.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
