hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (YARN-7763) Refactoring PlacementConstraintUtils APIs so PlacementProcessor/Scheduler can use the same API and implementation
Date Wed, 17 Jan 2018 00:00:02 GMT

     [ https://issues.apache.org/jira/browse/YARN-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wangda Tan reassigned YARN-7763:
--------------------------------

    Assignee: Arun Suresh

> Refactoring PlacementConstraintUtils APIs so PlacementProcessor/Scheduler can use the
same API and implementation
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7763
>                 URL: https://issues.apache.org/jira/browse/YARN-7763
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Wangda Tan
>            Assignee: Arun Suresh
>            Priority: Blocker
>
> As I mentioned on YARN-6599, we will add SchedulingRequest as part of the PlacementConstraintUtil
method and both of processor/scheduler implementation will use the same logic. The logic looks
like:
> {code:java}
> PlacementConstraint pc = schedulingRequest.getPlacementConstraint();
> If (pc == null) {
>   pc = PlacementConstraintMgr.getPlacementConstraint(schedulingRequest.getAllocationTags());
> }
> // Do placement constraint match ...{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message