You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2017/03/07 02:18:32 UTC
[jira] [Updated] (TEZ-3253) Remove special handling for last app
attempt (absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in AM env)
[ https://issues.apache.org/jira/browse/TEZ-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated TEZ-3253:
--------------------------------
Summary: Remove special handling for last app attempt (absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in AM env) (was: Handle absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in env of AM)
> Remove special handling for last app attempt (absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in AM env)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEZ-3253
> URL: https://issues.apache.org/jira/browse/TEZ-3253
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Hitesh Shah
> Assignee: Akira Ajisaka
> Fix For: 0.9.0
>
> Attachments: TEZ-3253.01.patch, TEZ-3253.02.patch, TEZ-3253.03.patch
>
>
> ApplicationConstants.MAX_APP_ATTEMPTS_ENV was removed in hadoop-3.x. This breaks max attempts handling and will cause the AM to unregister after only one attempt.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)