[
https://issues.apache.org/jira/browse/TEZ-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886723#comment-15886723
]
Siddharth Seth edited comment on TEZ-3253 at 2/27/17 11:12 PM:
---------------------------------------------------------------
Should we just remove this variable altogether in that case. similar to what
was done in MapReduce, and rely on YARN to not restart the last instance of the
app? - https://issues.apache.org/jira/browse/MAPREDUCE-5956
was (Author: sseth):
Should we just remove this variable altogether in that case. similar to what
was done in MapReduce, and rely on YARN to not restart the last instance of the
app?
> Handle absence of ApplicationConstants.MAX_APP_ATTEMPTS_ENV in env of AM
> ------------------------------------------------------------------------
>
> 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
> Attachments: TEZ-3253.01.patch, TEZ-3253.02.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)
