[
https://issues.apache.org/jira/browse/MAPREDUCE-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mudit Sharma updated MAPREDUCE-7339:
------------------------------------
Summary: Default Speculator returns speculationValue as
TOO_LATE_TO_SPECULATE or PROGRESS_IS_GOOD even if the task is
ALREADY_SPECULATING (was: Default Speculatoor returns speculationValue as
TOO_LATE_TO_SPECULATE or PROGRESS_IS_GOOD eve if the task is
ALREADY_SPECULATING)
> Default Speculator returns speculationValue as TOO_LATE_TO_SPECULATE or
> PROGRESS_IS_GOOD even if the task is ALREADY_SPECULATING
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-7339
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7339
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Mudit Sharma
> Priority: Major
>
> DefaultSpeculator implementation in Mapreduce returns some MAGIC numbers in
> speculationValue if the tasks is not a good candidate for speculation. It
> returns these values:
>
> {noformat}
> returns ALREADY_SPECULATING if that is true. This has priority.
> returns TOO_NEW if our companion task hasn't gotten any information
> returns PROGRESS_IS_GOOD if the task is sailing through
> returns NOT_RUNNING if the task is not running{noformat}
>
>
> {color:#172b4d}But there is one bug, due to which even if task is
> speculating, but if its progress is good or its too late to speculate, code
> returns TOO_LATE_TO_SPECULATE or PROGRESS_IS_GOOD and not
> ALREADY_SPECULATING{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
