[HDFS-6104] TestFsLimits#testDefaultMaxComponentLength Fails on branch-2

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 2.4.0
• Labels: java7
• Assignee: Unassigned
• Reporter: Mit Desai
• Created: 14/Mar/14 13:50
• Updated: 14/Mar/14 16:51
• Resolved: 14/Mar/14 16:51

Description

testDefaultMaxComponentLength fails intermittently with the following error

java.lang.AssertionError: expected:<0> but was:<255>
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.failNotEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:128)
	at org.junit.Assert.assertEquals(Assert.java:472)
	at org.junit.Assert.assertEquals(Assert.java:456)
	at org.apache.hadoop.hdfs.server.namenode.TestFsLimits.testDefaultMaxComponentLength(TestFsLimits.java:90)

On doing some research, I found that this is actually a JDK7 issue.
The test always fails when it runs after any test that runs addChildWithName() method

Issue Links

• relates to: HDFS-6102 Lower the default maximum items per directory to fix PB fsimage loading