[
https://issues.apache.org/jira/browse/TEZ-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041241#comment-15041241
]
Hitesh Shah commented on TEZ-2968:
----------------------------------
bq. It is fine to do it a separate jira. But I don't think we should remove the
limit, as I remember some users use the counter for some statistics as they use
it in MR.
Not sure I understand. My point was that instead of failing the job, we can
simply allow the user to configure disabling of the max. cap and therefore
never fail the job instead of changing the state machines to handle the limits
correctly i.e. change Limits.java to not throw an exception.
> Counter limits exception causes AM to crash
> --------------------------------------------
>
> Key: TEZ-2968
> URL: https://issues.apache.org/jira/browse/TEZ-2968
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Priority: Critical
> Attachments: TEZ-2968.1.wip.patch, TEZ-2968.2.patch, TEZ-2968.3.patch
>
>
> On vertex or dag completion, the counter limits exception propagates to the
> Dispatcher and causes the AM to die.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
