[
https://issues.apache.org/jira/browse/YARN-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306638#comment-16306638
]
Wangda Tan commented on YARN-7670:
----------------------------------
[~asuresh],
bq. YARN-6592 branch is up todate - I just rebased it with trunk and force
pushed - am guessing thats what you meant ?
Oh actually what I meant is merging the two commits, one is for the main change
and the other one is addendum fix. It's not necessary to commit addendum patch
to branch.
bq. 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 ?
It is true that we discussed this and it should not be a separate API, however,
the problem is current logic assumes "don't check pending resource". And the
only module needs this behavior is placement processor. Unless checking pending
resource is supported by the API, we can change other logic inside
CapacityScheduler to use the new added API.
> 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]
