[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

2017-01-06 Thread Junping Du (JIRA)

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

Junping Du updated YARN-3274:
-
Target Version/s:   (was: 2.8.0)

> FIFOScheduler should assign the same container number up to ResourceRequest 
> ask for ANY
> ---
>
> Key: YARN-3274
> URL: https://issues.apache.org/jira/browse/YARN-3274
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: scheduler
>Affects Versions: 2.7.0
>Reporter: Junping Du
>Assignee: Varun Saxena
>
> Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that 
> up to the number of containers specified in ResourceRequest for ANY which is 
> not true today. It only check number of ResourceRequest for ANY >0, then go 
> ahead to allocate containers according to other locality request which could 
> exceed the number in ANY. 
> This behavior is not consistent with other Schedulers, like: CS or FS, and 
> not meet our expectation, so we should fix this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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



[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

2015-02-27 Thread Junping Du (JIRA)

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

Junping Du updated YARN-3274:
-
Description: 
Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that 
up to the number of containers specified in ResourceRequest for ANY which is 
not true today. It only check number of ResourceRequest for ANY 0, then go 
ahead to allocate containers according to other locality request which could 
exceed the number in ANY. 
This behavior is not consistent with other Schedulers, like: CS or FS, and not 
meet our expectation, so we should fix this.

  was:Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers 
that up to the number of containers specified in ResourceRequest for ANY 


 FIFOScheduler should assign the same container number up to ResourceRequest 
 ask for ANY
 ---

 Key: YARN-3274
 URL: https://issues.apache.org/jira/browse/YARN-3274
 Project: Hadoop YARN
  Issue Type: Bug
  Components: scheduler
Affects Versions: 2.7.0
Reporter: Junping Du

 Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that 
 up to the number of containers specified in ResourceRequest for ANY which is 
 not true today. It only check number of ResourceRequest for ANY 0, then go 
 ahead to allocate containers according to other locality request which could 
 exceed the number in ANY. 
 This behavior is not consistent with other Schedulers, like: CS or FS, and 
 not meet our expectation, so we should fix this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

2015-02-27 Thread Junping Du (JIRA)

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

Junping Du updated YARN-3274:
-
Summary: FIFOScheduler should assign the same container number up to 
ResourceRequest ask for ANY  (was: FIFOScheduler should assign the same 
container number equal to ResourceRequest ask for ANY)

 FIFOScheduler should assign the same container number up to ResourceRequest 
 ask for ANY
 ---

 Key: YARN-3274
 URL: https://issues.apache.org/jira/browse/YARN-3274
 Project: Hadoop YARN
  Issue Type: Bug
  Components: scheduler
Affects Versions: 2.7.0
Reporter: Junping Du

 Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that 
 up to the number of containers specified in ResourceRequest for ANY 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)