[ 
https://issues.apache.org/jira/browse/YARN-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297754#comment-16297754
 ] 

Arun Suresh edited comment on YARN-7670 at 12/20/17 1:27 AM:
-------------------------------------------------------------

Updating patch with checkstyle fixes and added the extra warning.

[~kkaranasos], I did think of adding another {{tryCommit}} method, but decided 
not to - since I believe firstly that it is porbably better to make it explicit 
- so the caller is aware. And secondly, given the capacity scheduler is 
separated into 2 parts (Request Queuing and Actual commit/scheduling) maybe we 
should not think of it as the "default" way and keep the interfaces explicit as 
much as possible.


was (Author: asuresh):
Updating patch with checkstyle fixes.

[~kkaranasos], I did think of adding another {{tryCommit}} method, but decided 
not to - since I believe firstly that it is porbably better to make it explicit 
- so the caller is aware. And secondly, given the capacity scheduler is 
separated into 2 parts (Request Queuing and Actual commit/scheduling) maybe we 
should not think of it as the "default" way and keep the interfaces explicit as 
much as possible.

> 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
>         Attachments: YARN-7670-YARN-6592.001.patch, 
> YARN-7670-YARN-6592.002.patch, YARN-7670-YARN-6592.003.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]

Reply via email to