[
https://issues.apache.org/jira/browse/EAGLE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436578#comment-15436578
]
ASF GitHub Bot commented on EAGLE-492:
--------------------------------------
Github user haoch commented on the issue:
https://github.com/apache/incubator-eagle/pull/375
@DadanielZ very glad to see you to start to review and merge contributed
PR, just remind that you could also use
[`eagle-dev/merge-eagle-pr.py`](https://github.com/apache/incubator-eagle/blob/develop/eagle-dev/merge-eagle-pr.py)
besides manually doing it.
> Fix negative total execution time and make some code optimization for spark
> history job.
> ----------------------------------------------------------------------------------------
>
> Key: EAGLE-492
> URL: https://issues.apache.org/jira/browse/EAGLE-492
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Huizhi Lu
> Assignee: Huizhi Lu
> Fix For: v0.5.0
>
>
> 1) negative total execution time
> It is because the app was killed or terminated unexpectedly without
> completion. In the log file, it has only SparkListenerBlockManagerAdded
> timestamp. "Timestamp":1470768362299
> And the code initiated executor starttime with this timestamp.
> No executor or app endtime available, so executor endtime = 0L.
> Finally, totalExecutionTime = -1470768362299
> The code logic does not consider the situation when executor or app Endtime =
> 0L.
> Solution: If totalExecutionTime < 0L, set it = 0L. Stating the app is killed
> and not completed.
> 2) Url builder bug for completed jobs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
