[
https://issues.apache.org/jira/browse/YARN-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306636#comment-16306636
]
Arun Suresh commented on YARN-7670:
-----------------------------------
bq. Could you help to merge the commits using git hard push since we're in
branch.
YARN-6592 branch is up todate - I just rebased it with trunk and force pushed -
am guessing thats what you meant ?
bq. And also, the new added method in ResourceScheduler should not be used by a
module other than placement processor
So, my intention was that it would be a generic API - not something only the
Processor can use. My understanding from our previous discussions were that the
Scheduler itself is split into 2 phases: First is the Proposal phase and second
the Commit phase. I think the API introduced here is a formalization of the the
Commit phase - no ?
Given the de-coupling, I feel we should expose the later phase as a proper
public API to be used by future features.
> Modifications to the ResourceScheduler to support SchedulingRequests
> --------------------------------------------------------------------
>
> Key: YARN-7670
> URL: https://issues.apache.org/jira/browse/YARN-7670
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Fix For: YARN-6592
>
> Attachments: YARN-7670-YARN-6592.001.patch,
> YARN-7670-YARN-6592.002.patch, YARN-7670-YARN-6592.003.patch,
> YARN-7670-YARN-6592.addendum.patch
>
>
> As per discussions in YARN-7612. This JIRA tracks the changes to the
> ResourceScheduler interface and implementation in CapacityScheduler to
> support SchedulingRequests
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
