[ https://issues.apache.org/jira/browse/MAPREDUCE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829958#comment-16829958 ]
Masatake Iwasaki commented on MAPREDUCE-7198: --------------------------------------------- Should "mapreduce.task.stuck.timeout-ms = 0" mean disabling the timeout rather than "mapreduce.task.timeout = 0"? 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). > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org