[HDFS-10960] TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2
• Fix Version/s: 2.8.0, 3.0.0-alpha2
• Component/s: hdfs
• Target Version/s: 3.0.0-alpha2
• Assignee: Manoj Govindassamy
• Reporter: Manoj Govindassamy
• Created: 04/Oct/16 20:53
• Updated: 06/Jan/17 08:41
• Resolved: 18/Oct/16 18:53

Description

TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in the following verification.

  700     // If an IOException thrown from BlockReceiver#run, it triggers
  701     // DataNode#checkDiskError(). So we can test whether checkDiskError() is called,
  702     // to see whether there is IOException in BlockReceiver#run().
  703     assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck());
  704 

Error Message

expected:<0> but was:<6498109>
Stacktrace

java.lang.AssertionError: expected:<0> but was:<6498109>
	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.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703)
	at org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620)