[ https://issues.apache.org/jira/browse/YARN-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329831#comment-16329831 ]
Weiwei Yang commented on YARN-7763: ----------------------------------- Hi [~leftnoteasy] I am fine that to get YARN-6599 in first. The other public API is only used in test cases, I'll try remove that in next patch once YARN-6599 gets in. Thanks. > 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: Weiwei Yang > Priority: Blocker > Attachments: YARN-7763-YARN-6592.001.patch > > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org