[
https://issues.apache.org/jira/browse/MAPREDUCE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285709#comment-15285709
]
Haibo Chen commented on MAPREDUCE-6698:
---------------------------------------
The change is limited to the timeout value we set on the test. It is 20s now.
The new value 10 mins should be sufficiently long.
> Increase timeout on
> TestUnnecessaryBlockingOnHistoryFileInfo.testTwoThreadsQueryingDifferentJobOfSameUser
> ---------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6698
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6698
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.7.3
> Reporter: Haibo Chen
> Assignee: Haibo Chen
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
