You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "patrick white (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 20:18:52 UTC
[jira] [Created] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if
-Dmapreduce.job.maps.speculative.execution=false
Speculative Execution: speculative map tasks launched even if -Dmapreduce.job.maps.speculative.execution=false
--------------------------------------------------------------------------------------------------------------
Key: MAPREDUCE-3404
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: job submission
Affects Versions: 0.23.0
Environment: Hadoop version is: Hadoop 0.23.0.1110031628
10 node test cluster
Reporter: patrick white
When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
task launch, ran job as follows:
hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
-Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
/tmp/test_file_of_words* /tmp/file_of_words.out
Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
file was 4 times as large as others:
hadoop --config <config> fs -ls /tmp
Found 5 items
drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
-rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
-rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
-rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
-rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
Job launched 5 mappers despite spec exec set to false, output snippet:
org.apache.hadoop.mapreduce.JobCounter
NUM_FAILED_MAPS=1
TOTAL_LAUNCHED_MAPS=5
TOTAL_LAUNCHED_REDUCES=1
RACK_LOCAL_MAPS=5
SLOTS_MILLIS_MAPS=273540
SLOTS_MILLIS_REDUCES=212876
Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
launched is expected since spec exec = true.
job run:
hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
-Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
/tmp/test_file_of_words* /tmp/file_of_words.out
output snippet:
org.apache.hadoop.mapreduce.JobCounter
NUM_FAILED_MAPS=1
TOTAL_LAUNCHED_MAPS=5
TOTAL_LAUNCHED_REDUCES=1
RACK_LOCAL_MAPS=5
SLOTS_MILLIS_MAPS=279653
SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185996#comment-13185996 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Commit #366 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/366/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
svn merge --ignore-ancestry -c 1231395 ../../trunk/
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231397
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186194#comment-13186194 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #138 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/138/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
svn merge --ignore-ancestry -c 1231395 ../../trunk/
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231397
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185997#comment-13185997 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1615 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1615/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231395
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158604#comment-13158604 ]
Eric Payne commented on MAPREDUCE-3404:
---------------------------------------
I have two corrections to make and three observation.
* Corrections:
** The property name that controls mapper speculative execution is {{mapreduce.map.speculative}} rather than
{{mapreduce.job.maps.speculative.execution}}.
** The property name that controls reduce speculative execution is {{mapreduce.reduce.speculative}} rather than
{{mapreduce.job.reduces.speculative.execution}}.
* Observations:
** If the config values are set as follows in the _mapred-site.xml_ file, then overriding of {{mapreduce.map.speculative}}
works as expected on the command line:
{noformat}
<property>
<name>mapreduce.map.speculative</name>
<value>true</value>
</property>
<property>
<name>mapreduce.reduce.speculative</name>
<value>false</value>
</property>
{noformat}
*** That is, -Dmapreduce.map.speculative=false on the command line will override the value in the config file and turn
off speculative map execution.
** However, if mapreduce.reduce.speculative is set to true in the config file (as in the following example), it is not
possible to turn off speculative *map* execution on the command line. For some reason, setting
mapreduce.reduce.speculative to true in the config file overrides the command line value of mapreduce.map.speculative
{noformat}
<property>
<name>mapreduce.map.speculative</name>
<value>true</value>
</property>
<property>
<name>mapreduce.reduce.speculative</name>
<value>true</value>
</property>
{noformat}
** Also, if the config file sets {{mapreduce.map.speculative}} to {{false}} but leaves {{mapreduce.reduce.speculative}} set to {{true}}, the speculative execution still happens for the mappers even though {{mapreduce.reduce.speculative}} is {{false}}. So, this is not just a command line override issue.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Vinod Kumar Vavilapalli (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-3404:
-----------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.23.0)
Release Note: Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
..oh, and the tests look good too.
Just committed this to trunk and branch-0.23. Thanks Eric!
On a side note, not caused by this patch, it is not correct that we increment the num_failed_maps counter when the speculation kills a task. Instead we should have a num_killed_maps. Separate issue, will file a ticket.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Status: Patch Available (was: Open)
In addition to the new unit test, I have successfully tested this patch on a 10-node cluster.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186200#comment-13186200 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #160 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/160/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
svn merge --ignore-ancestry -c 1231395 ../../trunk/
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231397
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Robert Joseph Evans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169602#comment-13169602 ]
Robert Joseph Evans commented on MAPREDUCE-3404:
------------------------------------------------
I have a couple of comments.
# In your test TestSpeculativeExecution.java line 65 (I think) and also later in the file, there is some code commented out. It should probably just be deleted.
# In the mapper code that checks for the first attempt of the first mapper, I would prefer to see it not do a string comparison as that value could change in the future. I would rather see it check the individual parts of the ID though the APIs it provides.
# Why are you calling Thread.currentThread() right before the call to sleep()? this should probably be deleted.
# It looks like there might be some tabs in the patch. Please replace them with spaces.
# The boolean expression {code}
( ( conf.getBoolean(MRJobConfig.MAP_SPECULATIVE, false)
&& (tType == null || tType == TaskType.MAP) )
|| ( conf.getBoolean(MRJobConfig.REDUCE_SPECULATIVE, false)
&& (tType == null || tType == TaskType.REDUCE)) ) ) {
{code} is so complex that you needed comment to explain what it was doing. Also those conf values are not going to change from the time that the AM is launched. Could you please cache them. I think it would clean up the expression a lot.
# When will tType be null? and why do we want to pass it on to the Speculator when it is? I dug and it looks like it is null when the event type is JOB_CREATE or ATTEMPT_STATUS_UPDATE, but it would be good to document that in the javadocs for the Speculator interface (So that others can override that functionality in the future). It would also be cleaner imo to have the tType == null check be in a different place form the tType == Map or tType == REDUCE. But I really don't care so long as there is a comment explaining what is happening.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185999#comment-13185999 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1542 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1542/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231395
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Attachment: MAPREDUCE-3404.2.txt
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if
-Dmapreduce.job.maps.speculative.execution=false
Posted by "Eric Payne (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne reassigned MAPREDUCE-3404:
-------------------------------------
Assignee: Eric Payne
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.job.maps.speculative.execution=false
> --------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186207#comment-13186207 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #958 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/958/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231395
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Fix Version/s: 0.24.0
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.0, 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186190#comment-13186190 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #925 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/925/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231395
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Vinod Kumar Vavilapalli (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185986#comment-13185986 ]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3404:
----------------------------------------------------
bq. How do we make sure that if mapreduce.job.maps.speculative=false and mapreduce.job.reduce.speculative=true, the maps dont get speculated and the reduces gets speculated?
The speculator handles map and reduce speculation separately. I just looked at the patch, and it achieves the above by not sending any map events to the speculative when map-speculation is disabled. The speculator doesn't seem to find any maps to speculates (as it doesn't know about any maps at all) and so only speculates reduces. Works (IMO) a convoluted way but can live with that.
+1 for the patch. Pushing this in.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.0, 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184454#comment-13184454 ]
Hadoop QA commented on MAPREDUCE-3404:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12510252/MAPREDUCE-3404.2.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1595//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1595//console
This message is automatically generated.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.0, 0.23.1
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Attachment: MAPREDUCE-3404.1.txt
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if
-Dmapreduce.job.maps.speculative.execution=false
Posted by "Mahadev konar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3404:
-------------------------------------
Component/s: mrv2
Priority: Critical (was: Major)
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.job.maps.speculative.execution=false
> --------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Priority: Critical
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186024#comment-13186024 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1560 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1560/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231395
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169999#comment-13169999 ]
Mahadev konar commented on MAPREDUCE-3404:
------------------------------------------
@Eric,
How do we make sure that if mapreduce.job.maps.speculative=false and mapreduce.job.reduce.speculative=true, the maps dont get speculated and the reduces gets speculated?
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186011#comment-13186011 ]
Hudson commented on MAPREDUCE-3404:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #388 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/388/])
MAPREDUCE-3404. Corrected MR AM to honor speculative configuration and enable speculating either maps or reduces. Contributed by Eric Payne.
svn merge --ignore-ancestry -c 1231395 ../../trunk/
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1231397
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestSpeculativeExecution.java
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.24.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Fix Version/s: 0.23.0
0.23.1
Status: Patch Available (was: Open)
@Bobby,
> 1. TestSpeculativeExecution.java: ... code commented out.
Removed
> 2. TestSpeculativeExecution.java: ... have mapper check the individual parts of the ID though the APIs...
Done
> 3. TestSpeculativeExecution.java: ... don't call Thread.currentThread() ...
Removed.
> 4. TestSpeculativeExecution.java: ... remove tabs ...
Done.
> 5. MRAppMaster.java: ... Simplify boolean expression ...
Done.
> 6. TestSpeculativeExecution.java: ... Override speculator so that it will cause speculation to happen ...
Done.
@Mahadev:
> How do we make sure that if mapreduce.job.maps.speculative=false and mapreduce.job.reduce.speculative=true, the maps dont get speculated and the reduces gets speculated?
I added a test case that covers speculation for reduces only.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Fix For: 0.23.1, 0.23.0
>
> Attachments: MAPREDUCE-3404.1.txt, MAPREDUCE-3404.2.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169605#comment-13169605 ]
Hadoop QA commented on MAPREDUCE-3404:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507391/MAPREDUCE-3404.1.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1450//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1450//console
This message is automatically generated.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated MAPREDUCE-3404:
-------------------------------------
Status: Open (was: Patch Available)
Cancelling patch while Mahadev's comments are addressed.
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-3404.1.txt
>
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3404) Speculative Execution:
speculative map tasks launched even if -Dmapreduce.map.speculative=false
Posted by "Eric Payne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-3404:
----------------------------------
Summary: Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false (was: Speculative Execution: speculative map tasks launched even if -Dmapreduce.job.maps.speculative.execution=false)
> Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3404
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3404
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: job submission, mrv2
> Affects Versions: 0.23.0
> Environment: Hadoop version is: Hadoop 0.23.0.1110031628
> 10 node test cluster
> Reporter: patrick white
> Assignee: Eric Payne
> Priority: Critical
>
> When forcing a mapper to take significantly longer than other map tasks, speculative map tasks are
> launched even if the mapreduce.job.maps.speculative.execution parameter is set to 'false'.
> Testcase: ran default WordCount job with spec execution set to false for both map and reduce but still saw a fifth mapper
> task launch, ran job as follows:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=false -Dmapreduce.job.reduces.speculative.execution=false
> /tmp/test_file_of_words* /tmp/file_of_words.out
> Input data was 4 text files >hdfs blocksize, with same word pattern plus one diff text line in each file, fourth
> file was 4 times as large as others:
> hadoop --config <config> fs -ls /tmp
> Found 5 items
> drwxr-xr-x - user hdfs 0 2011-10-20 16:17 /tmp/file_of_words.out
> -rw-r--r-- 3 user hdfs 62800021 2011-10-20 14:45 /tmp/test_file_of_words1
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words2
> -rw-r--r-- 3 user hdfs 62800024 2011-10-20 14:46 /tmp/test_file_of_words3
> -rw-r--r-- 3 user hdfs 271708312 2011-10-20 15:50 /tmp/test_file_of_words4
> Job launched 5 mappers despite spec exec set to false, output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=273540
> SLOTS_MILLIS_REDUCES=212876
> Reran same case as above only set both spec exec params to 'true', same results only this time the fifth task being
> launched is expected since spec exec = true.
> job run:
> hadoop --config <config> jar /tmp/testphw/wordcount.jar WordCount
> -Dmapreduce.job.maps.speculative.execution=true -Dmapreduce.job.reduces.speculative.execution=true
> /tmp/test_file_of_words* /tmp/file_of_words.out
> output snippet:
> org.apache.hadoop.mapreduce.JobCounter
> NUM_FAILED_MAPS=1
> TOTAL_LAUNCHED_MAPS=5
> TOTAL_LAUNCHED_REDUCES=1
> RACK_LOCAL_MAPS=5
> SLOTS_MILLIS_MAPS=279653
> SLOTS_MILLIS_REDUCES=211474
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira