[HDFS-4633] TestDFSClientExcludedNodes fails sporadically if excluded nodes cache expires too quickly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0, 3.0.0-alpha1
• Fix Version/s: 2.3.0
• Component/s: hdfs-client, test
• Target Version/s: 2.3.0
• Hadoop Flags: Reviewed
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 25/Mar/13 19:35
• Updated: 12/May/16 18:13
• Resolved: 27/Mar/13 20:50

Description

TestDFSClientExcludedNodes simulates failures of individual data nodes in the client's write pipeline and checks the client's ability to recover. HDFS-4246 added support for periodic "forgiveness" by caching the list of known bad data nodes with a periodic eviction. The test uses a 1 second cache expiration. This sometimes causes failed nodes to be forgiven too fast and violate the assumptions of the test.

Issue Links

• is broken by: HDFS-4246 The exclude node list should be more forgiving, for each output stream
• relates to: HDFS-3602 Enhancements to HDFS for Windows Server and Windows Azure development and runtime environments