[jira] [Updated] (MAPREDUCE-3404) Speculative Execution: speculative map tasks launched even if -Dmapreduce.map.speculative=false

2012-01-13 Thread Vinod Kumar Vavilapalli (Updated) (JIRA)

 [ 
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   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   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   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

2012-01-12 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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

2012-01-11 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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

2012-01-11 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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

2011-12-20 Thread Arun C Murthy (Updated) (JIRA)

 [ 
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   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   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   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

2011-12-14 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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

2011-12-14 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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

2011-11-28 Thread Eric Payne (Updated) (JIRA)

 [ 
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   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   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   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