closing, thank you [~tarunparimi] for your contribution
> Speculative execution behavior is observed even when
> mapreduce.map.speculative and mapreduce.reduce.speculative are
Tarun Parimi created MAPREDUCE-7278:
---
Summary: Speculative execution behavior is observed even when
mapreduce.map.speculative and mapreduce.reduce.speculative are false
Key: MAPREDUCE-7278
URL: https
Kihwal Lee created MAPREDUCE-7177:
-
Summary: Disable speculative execution in TestDFSIO
Key: MAPREDUCE-7177
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7177
Project: Hadoop Map/Reduce
Peter Bacsko created MAPREDUCE-7144:
---
Summary: Speculative execution can cause race condition
Key: MAPREDUCE-7144
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7144
Project: Hadoop Map/Reduce
g a task during speculative execution
> --
>
> Key: MAPREDUCE-3294
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3294
> Project: Hadoop Map/Reduce
> Is
zhihai xu created MAPREDUCE-6143:
Summary: add configuration for mapreduce speculative execution in
MR2
Key: MAPREDUCE-6143
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6143
Project: Hadoop
[
https://issues.apache.org/jira/browse/MAPREDUCE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-2062.
-
Resolution: Fixed
Spec exec got majorly overhauled. Closing.
> speculat
.
> Improve speculative execution
> -
>
> Key: MAPREDUCE-2039
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2039
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>
Gera Shegalov created MAPREDUCE-5692:
Summary: Add explicit diagnostics when a task attempt is killed
due to speculative execution
Key: MAPREDUCE-5692
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5692
Tassapol Athiapinya created MAPREDUCE-5533:
--
Summary: Speculative execution does not function for reduce
Key: MAPREDUCE-5533
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5533
Project
Under YARN (branch-2, branch-0.23, and trunk) the speculative execution
decision is pluggable, and can be replaced by a user. If you could come
up with a better solution to speculative execution that would be great.
We have known for a while that it is not very good (most of the time we
run a
Hello Sir/Madam
I am doing PhD. I am interested to do research in Hadoop for publishing
paper.
I know little bit about speculative execution of slow tasks. I know it is
possible to enable or disable speculative execution.
But,
Is there any idea published already for dynamically enable
Reporter: Runping Qi
>
> One mapper of my job stuck when it reached 87.7%.
> Speculative execution was set to true.
> But no speculative execution was fired for that task.
> The whole job was stalled.
--
This message is automatically generated by JIRA.
If you think it was sen
ask stuck at 95.71% for a long time and the speculative execution
> does not kick in
> --
>
> Key: MAPREDUCE-92
> URL: https://issues.apache.org/jira/b
Speculative execution algorithm in 1.0 is too pessimistic in many cases
---
Key: MAPREDUCE-3895
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3895
Project: Hadoop Map/Reduce
Speculative Execution: speculative map tasks launched even if
-Dmapreduce.job.maps.speculative.execution=false
--
Key: MAPREDUCE-3404
URL: https
Speculative Execution: enabling multiple reduce tasks inhibit spec exec launch
of mappers
--
Key: MAPREDUCE-3403
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3403
Log the reason for killing a task during speculative execution
--
Key: MAPREDUCE-3294
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3294
Project: Hadoop Map/Reduce
Issue
speculative execution does not handle cases where stddev > mean well
Key: MAPREDUCE-2162
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2162
Project: Hadoop Map/Red
speculative execution is too aggressive under certain conditions
Key: MAPREDUCE-2062
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2062
Project: Hadoop Map/Reduce
Issue
Improve speculative execution
-
Key: MAPREDUCE-2039
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2039
Project: Hadoop Map/Reduce
Issue Type: Improvement
Reporter: Dick King
Allow users to do speculative execution of a task manually
--
Key: MAPREDUCE-1608
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1608
Project: Hadoop Map/Reduce
Issue Type: New
Sqoop should disable speculative execution in export
Key: MAPREDUCE-1469
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1469
Project: Hadoop Map/Reduce
Issue Type: Bug
-5869
> Prior code fix in Capacity Scheduler prevents speculative execution in jobs
> ---
>
> Key: MAPREDUCE-513
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-513
>
Support for per-phase speculative execution
---
Key: MAPREDUCE-718
URL: https://issues.apache.org/jira/browse/MAPREDUCE-718
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components
Fix some corner case issues in speculative execution (post hadoop-2141)
---
Key: MAPREDUCE-717
URL: https://issues.apache.org/jira/browse/MAPREDUCE-717
Project: Hadoop Map/Reduce
26 matches
Mail list logo