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 "Akira Ajisaka (JIRA)" <ji...@apache.org> on 2019/05/07 07:07:00 UTC
[jira] [Updated] (MAPREDUCE-7198) mapreduce.task.timeout=0
configuration used to disable timeout doesn't work
[ https://issues.apache.org/jira/browse/MAPREDUCE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akira Ajisaka updated MAPREDUCE-7198:
-------------------------------------
Attachment: MAPREDUCE-7198.02.patch
> mapreduce.task.timeout=0 configuration used to disable timeout doesn't work
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-7198
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7198
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Akira Ajisaka
> Assignee: Akira Ajisaka
> Priority: Minor
> Attachments: MAPREDUCE-7198.01.patch, MAPREDUCE-7198.02.patch
>
>
> mapreduce.task.timeout=0 configuration used to disable timeout doesn't work after MAPREDUCE-6190. If the task timeout is configured as zero the task fails with stuck timeout, if the TaskStatus is null.
> {code}
> if (sendProgress) {
> // we need to send progress update
> updateCounters();
> checkTaskLimits();
> taskStatus.statusUpdate(taskProgress.get(),
> taskProgress.toString(),
> counters);
> amFeedback = umbilical.statusUpdate(taskId, taskStatus);
> taskFound = amFeedback.getTaskFound();
> taskStatus.clearStatus();
> }
> else {
> // send ping
> amFeedback = umbilical.statusUpdate(taskId, null);
> taskFound = amFeedback.getTaskFound();
> }
> {code}
> This issue is reported by [~bibinchundatt].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org