[
https://issues.apache.org/jira/browse/YARN-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328202#comment-16328202
]
Wangda Tan commented on YARN-6619:
----------------------------------
[~asuresh] , could u update java doc to mark unstable of this API?
{quote}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
{quote}
I'm not sure if I verified this, but in my mind, a SchedulingRequest without
PlacementConstraint should be treated same as ResourceRequest with resourceName
= *. I'm not sure if we should associate an empty tag or default tag with the
container with null allocation tag, maybe we shouldn't. Since this isn't
related to the Jira, let's decide it later.
> 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]
