[
https://issues.apache.org/jira/browse/SPARK-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346951#comment-14346951
]
Apache Spark commented on SPARK-6159:
-------------------------------------
User 'viirya' has created a pull request for this issue:
https://github.com/apache/spark/pull/4891
> Distinguish between inprogress and abnormal event log history
> -------------------------------------------------------------
>
> Key: SPARK-6159
> URL: https://issues.apache.org/jira/browse/SPARK-6159
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Liang-Chi Hsieh
> Priority: Minor
>
> This is the following up of SPARK-6107. Currently, when an application is
> terminated abnormally (ex. Ctrl + C), its log file is still in ".inprogress"
> format. SPARK-6107 makes the inprogress log readable to SparkUI.
> However, I think we should be able to distinguish between real inprogress
> case and abnormal case. So this fixing tries to add a shutdownhook to
> EventLoggingListener and rename ".inprogress" log to ".abnormal" log.
> Then we can know what it is the case when reading log in rebuildSparkUI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
