[
https://issues.apache.org/jira/browse/TEZ-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211003#comment-15211003
]
Jason Lowe commented on TEZ-2278:
---------------------------------
bq. it might be better to have a slightly different event ( history only )
which ends up setting the launch time and also modifies status to RUNNING
That sounds OK to me, but do we really want to set the current
TaskStartedEvent's start time to zero as well? I'm not sure what existing
consumers of the event will do if it suddenly starts showing up as zero. If
they'll all be fine with it then that would be one way to signal the consumer
that a subsequent task running event can be expected.
> Tez UI start/end time and duration shown are wrong for tasks
> ------------------------------------------------------------
>
> Key: TEZ-2278
> URL: https://issues.apache.org/jira/browse/TEZ-2278
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Affects Versions: 0.6.0
> Reporter: Rohini Palaniswamy
> Assignee: Jason Lowe
> Attachments: TEZ-2278.001.patch, screenshot-1.png, screenshot-2.png,
> screenshot-3.png, screenshot-4.png
>
>
> Observing lot of time discrepancies between vertex, task and swinlane views.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
