[
https://issues.apache.org/jira/browse/TEZ-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726833#comment-14726833
]
Bikas Saha commented on TEZ-2752:
---------------------------------
That is precisely the reason for the change. The UI or anything else that uses
ATS will see an incorrect execution time interval for an attempt with lost
outputs. Say attempt finishes at time T with execution time of 1m and then
after 1 hour output lost is reported. That attempt will appear to have run for
an hour even though it actually ran for 1m. If the time for losing the output
is needed (not sure if it is right now) then that can be tracked separately.
Does that clarify?
> logUnsuccessful completion in Attempt should write original finish time to ATS
> ------------------------------------------------------------------------------
>
> Key: TEZ-2752
> URL: https://issues.apache.org/jira/browse/TEZ-2752
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-2752.1.patch
>
>
> Currently it overwrites with the current time and that results in wrong
> information since in reality the attempt might have finished earlier if the
> failure was output failure. Other failures also set the finish time in the
> terminate transition and thus even in non output failed cases the value of
> finishtime can be used instead of using current time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
