hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira Ajisaka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7198) mapreduce.task.timeout=0 configuration used to disable timeout doesn't work
Date Tue, 07 May 2019 06:57:00 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834436#comment-16834436
] 

Akira Ajisaka commented on MAPREDUCE-7198:
------------------------------------------

Thanks [~iwasakims] for the comment.

bq. Should "mapreduce.task.stuck.timeout-ms = 0" mean disabling the timeout rather than "mapreduce.task.timeout
= 0"?
Agreed.

bq. If the goal here is to retain previous behaviour before MAPREDUCE-6190 as task does not
timeout only if mapreduce.task.timeout = 0, the task-stuck-timeout should be disabled by default
(by set the value to 0).
My understanding is that the goal here is to provide some way to disable task timeout for
testing purpose, so I'm thinking we don't need to disable the stuck timeout by default.

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


Mime
View raw message