[MAPREDUCE-6698] Increase timeout on TestUnnecessaryBlockingOnHistoryFileInfo.testTwoThreadsQueryingDifferentJobOfSameUser

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: jobhistoryserver
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Haibo Chen
• Reporter: Haibo Chen
• Created: 17/May/16 00:17
• Updated: 30/Aug/16 01:13
• Resolved: 17/May/16 15:07

Description

The timeout on TestUnnecessaryBlockingOnHistoryFileInfo.testTwoThreadsQueryingDifferentJobOfSameUser is added to verify the fix of MAPREDUCE-6684 works. When two thread are requesting different jobs owned by the same user, one thread request jobA should not be blocked by the other that is processing a large job jobB. The timeout exception, if happened, should ideally indicate the fix does not work. But the timeout period is set too aggressive, so the test always fails on slow VMs.

Issue Links

• relates to: MAPREDUCE-6684 High contention on scanning of user directory under immediate_done in Job History Server