You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2015/12/04 17:57:11 UTC

[jira] [Updated] (TEZ-2966) Tez does not honor mapreduce.task.timeout

     [ https://issues.apache.org/jira/browse/TEZ-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles updated TEZ-2966:
---------------------------------
    Attachment: TEZ-2966.1.patch

> Tez does not honor mapreduce.task.timeout
> -----------------------------------------
>
>                 Key: TEZ-2966
>                 URL: https://issues.apache.org/jira/browse/TEZ-2966
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>         Attachments: TEZ-2966.1.patch
>
>
> Tez use to use directly the setting from mapreduce.task.timeout before TEZ-761. It will be good to honor this setting.
> Based on the discussion in TEZ-2918 there are some decisions to still consider.
> https://issues.apache.org/jira/browse/TEZ-2918?focusedCommentId=14990498&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14990498
> If a deprecated key is added to honor the mapreduce.task.timeout setting, which setting does this best represent in tez (container ping timeout, task ping timeout, or task progress timeout)?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)