[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Lowe updated MAPREDUCE-6698:
----------------------------------
    Affects Version/s:     (was: 2.7.3)
                       2.8.0
     Target Version/s: 2.8.0  (was: 2.7.3)

TestUnnecessaryBlockingOnHistoryFileInfo doesn't exist in branch-2.7.  
Adjusting the affects/target versions accordingly.

> 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.8.0
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>         Attachments: mapreduce6698.001.patch
>
>
> 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: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

Reply via email to