[
https://issues.apache.org/jira/browse/YARN-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328195#comment-16328195
]
Arun Suresh commented on YARN-6619:
-----------------------------------
Update the patch (v003) based on [~kkaranasos]'s and [~leftnoteasy]'s
suggestions.
* Removed the {{addPlacementConstratint}} method and included it as an optional
parameter in the register call.
* as per wangda's suggestion, am now just updating the numAllocations instead
of adding.
* moved the scheduler matching check to a separate function - and removed the
resource sizing equality check
bq. If there are no tags, do we still associate a constraint with an empty tag?
If there are no tags in the scheduling request, then the scheduler should
expect a Placement Constraint, which applies to that specific scheduling
request - that check I guess is done in YARN-6599
> AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest
> objects
> --------------------------------------------------------------------------------
>
> Key: YARN-6619
> URL: https://issues.apache.org/jira/browse/YARN-6619
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Priority: Major
> Attachments: YARN-6619-YARN-6592.001.patch,
> YARN-6619-YARN-6592.002.patch, YARN-6619-YARN-6592.003.patch
>
>
> Opening this JIRA to track changes needed in the AMRMClient to incorporate
> the PlacementConstraint and SchedulingRequest objects
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
