[TEZ-2966] Tez does not honor mapreduce.task.timeout

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7.1, 0.8.2
• Target Version/s: 0.7.1
• Assignee: Jonathan Turner Eagles
• Reporter: Jonathan Turner Eagles
• Created: 01/Dec/15 18:20
• Updated: 18/May/16 04:55
• Resolved: 11/Dec/15 16:27

Description

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)?

Issue Links

• is related to: TEZ-3141 mapreduce.task.timeout is not translated to container heartbeat timeout