[
https://issues.apache.org/jira/browse/MAPREDUCE-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759642#comment-16759642
]
Hudson commented on MAPREDUCE-7177:
-----------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15874 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15874/])
MAPREDUCE-7177. Disable speculative execution in TestDFSIO. Contributed
(aajisaka: rev c991e2ca5a65eae62bad7e5baf81f1eb633b7ec0)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/fs/TestDFSIO.java
> Disable speculative execution in TestDFSIO
> ------------------------------------------
>
> Key: MAPREDUCE-7177
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7177
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 3.2.0, 2.8.5
> Reporter: Kihwal Lee
> Assignee: Zhaohui Xin
> Priority: Major
> Fix For: 2.10.0, 3.1.2, 2.8.6, 3.3.0, 3.2.1, 2.9.3
>
> Attachments: MAPREDUCE-7177.001.patch
>
>
> When TestDFSIO runs in a certain environment where a subset of mappers are
> slow, the speculative execution can start. In the write phase, this will
> make existing mapper to fail in next addBlock() since the output files are
> overwritten.
> To make the benchmark more predictable and repeatable, speculation must be
> implicitly disabled in TestDFSIO itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
