[YARN-3833] TestWorkPreservingRMRestart#testSchedulerRecovery fails in trunk

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: resourcemanager
• Assignee: Unassigned
• Reporter: Jun Gong
• Created: 19/Jun/15 14:18
• Updated: 19/Jun/15 14:47
• Resolved: 19/Jun/15 14:46

Description

Running org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart
Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 282.811 sec <<< FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart
testSchedulerRecovery[1](org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart)  Time elapsed: 6.445 sec  <<< FAILURE!
java.lang.AssertionError: expected:<6144> but was:<8192>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:555)
	at org.junit.Assert.assertEquals(Assert.java:542)
	at org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart.assertMetrics(TestWorkPreservingRMRestart.java:853)
	at org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart.checkFSQueue(TestWorkPreservingRMRestart.java:342)
	at org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart.testSchedulerRecovery(TestWorkPreservingRMRestart.java:241)

Issue Links

• duplicates: YARN-3790 usedResource from rootQueue metrics may get stale data for FS scheduler after recovering the container