[
https://issues.apache.org/jira/browse/TEZ-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989677#comment-15989677
]
Harish Jaiprakash commented on TEZ-3700:
----------------------------------------
* killSelf is not using message being sent as argument.
* Should we use ConcurrentHashMap instead of synchronizedMap?
* We do not remove from failedTaskIds, is that alright?
> Consumer attempt should kill itself instead of failing during validation
> checks with final merge avoidance
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEZ-3700
> URL: https://issues.apache.org/jira/browse/TEZ-3700
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-3700.1.patch, TEZ-3700.2.patch, TEZ-3700.3.patch
>
>
> Currently when if data is received from different attempts with final merge
> disabled (with/without pipleining), consumer attempt ends up with failure.
> Instead it should issue kill request so that the job deos not end up with
> failures.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
