[HDFS-10962] TestRequestHedgingProxyProvider is flaky

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.4
• Fix Version/s: 2.8.0, 3.0.0-alpha2
• Component/s: test
• Target Version/s: 2.8.0, 3.0.0-alpha2
• Assignee: Andrew Wang
• Reporter: Andrew Wang
• Created: 05/Oct/16 04:31
• Updated: 05/Oct/16 22:20
• Resolved: 05/Oct/16 22:14

Description

This test fails occasionally with an error like this:

org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails


Error Message

Wanted but not invoked:
namenodeProtocols.getStats();
-> at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
Actually, there were zero interactions with this mock.
Stacktrace

org.mockito.exceptions.verification.WantedButNotInvoked: 
Wanted but not invoked:
namenodeProtocols.getStats();
-> at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
Actually, there were zero interactions with this mock.

	at org.apache.hadoop.hdfs.server.namenode.ha.TestRequestHedgingProxyProvider.testHedgingWhenOneFails(TestRequestHedgingProxyProvider.java:78)
Standard Output

2016-09-26 15:26:02,234 WARN  hdfs.DFSUtil (DFSUtil.java:getAddressesForNameserviceId(689)) - Namenode for mycluster-26780990 remains unresolved for ID nn1.  Check your hdfs-site.xml file to ensure namenodes are configured properly.
2016-09-26 15:26:02,340 WARN  hdfs.DFSUtil (DFSUtil.java:getAddressesForNameserviceId(689)) - Namenode for mycluster-26780990 remains unresolved for ID nn2.  Check your hdfs-site.xml file to ensure namenodes are configured properly.