You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Liang-Chi Hsieh (JIRA)" <ji...@apache.org> on 2015/03/06 13:58:38 UTC
[jira] [Closed] (SPARK-6159) Distinguish between inprogress and
abnormal event log history
[ https://issues.apache.org/jira/browse/SPARK-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liang-Chi Hsieh closed SPARK-6159.
----------------------------------
Resolution: Won't Fix
> 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
> Affects Versions: 1.0.0
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org