[
https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated YARN-2604:
--------------------------------
Attachment: YARN-2604.patch
The new patch fixes the test failures:
- TestContainerAllocation: Minor adjustment to memory allocation amount
- TestFairScheduler: This failing test becomes obsolete with the patch, so I
removed it
- TestCapacityScheduler: I had to use more fine-grained locking on
{{maximumAllocation}} to fix this, so I gave it it's own
{{ReentrantReadWriteLock}} instead of just using {{synchronized}}
- (TestAMRestart was unrelated)
> Scheduler should consider max-allocation-* in conjunction with the largest
> node
> -------------------------------------------------------------------------------
>
> Key: YARN-2604
> URL: https://issues.apache.org/jira/browse/YARN-2604
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.5.1
> Reporter: Karthik Kambatla
> Assignee: Robert Kanter
> Attachments: YARN-2604.patch, YARN-2604.patch
>
>
> If the scheduler max-allocation-* values are larger than the resources
> available on the largest node in the cluster, an application requesting
> resources between the two values will be accepted by the scheduler but the
> requests will never be satisfied. The app essentially hangs forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
