YARN-5082. Limit ContainerId increase in fair scheduler if the num of node app reserved reached the limit. Addendum to fix javac warning. (Arun Suresh via kasha)
This commit is contained in:
parent
0761379fe4
commit
fbbe0bb627
@ -4512,7 +4512,7 @@ public void testContainerAllocationWithContainerIdLeap() throws Exception {
|
||||
scheduler.handle(new NodeUpdateSchedulerEvent(node2));
|
||||
|
||||
assertEquals(4096, scheduler.getQueueManager().getQueue("queue1").
|
||||
getResourceUsage().getMemory());
|
||||
getResourceUsage().getMemorySize());
|
||||
|
||||
//container will be reserved at node1
|
||||
RMContainer reservedContainer1 =
|
||||
@ -4532,7 +4532,7 @@ public void testContainerAllocationWithContainerIdLeap() throws Exception {
|
||||
app1, RMAppAttemptState.KILLED, false));
|
||||
|
||||
assertEquals(0, scheduler.getQueueManager().getQueue("queue1").
|
||||
getResourceUsage().getMemory());
|
||||
getResourceUsage().getMemorySize());
|
||||
|
||||
// container will be allocated at node2
|
||||
scheduler.handle(new NodeUpdateSchedulerEvent(node2));
|
||||
|
Loading…
Reference in New Issue
Block a user