tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-3141) mapreduce.task.timeout is not translated to container heartbeat timeout
Date Fri, 26 Feb 2016 14:54:18 GMT

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

Jason Lowe updated TEZ-3141:
    Attachment: TEZ-3141.002.patch

I believe Pig does use the DAG key map directly.  [~rohini] can clarify.

As for removing it from the runtime map, I left it there because this property not only maps
to the container heartbeat timeout but also the task heartbeat timeout.  I thought theoretically
one could set a different timeout for tasks of one vertex vs. another, but in practice this
is probably not the case.  I hedged and left it in the runtime map since it doesn't really
hurt to have it there as well, but here's a patch that removes the runtime changes and leaves
it only in the DAG map.

> mapreduce.task.timeout is not translated to container heartbeat timeout
> -----------------------------------------------------------------------
>                 Key: TEZ-3141
>                 URL: https://issues.apache.org/jira/browse/TEZ-3141
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.7.1
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: TEZ-3141.001.patch, TEZ-3141.002.patch
> TEZ-2966 added the deprecation to the runtime key map, but the container  timeout is
an AM-level property and therefore the runtime map translation is missed.

This message was sent by Atlassian JIRA

View raw message