You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/10/05 16:31:27 UTC

[jira] [Resolved] (SPARK-5783) Include filename, line number in eventlog-parsing error message

     [ https://issues.apache.org/jira/browse/SPARK-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-5783.
------------------------------
       Resolution: Fixed
         Assignee: Ryan Williams
    Fix Version/s: 1.4.0
                   1.3.2

Actually looks like this was resolved a while ago, for 1.3.2+

> Include filename, line number in eventlog-parsing error message
> ---------------------------------------------------------------
>
>                 Key: SPARK-5783
>                 URL: https://issues.apache.org/jira/browse/SPARK-5783
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Ryan Williams
>            Assignee: Ryan Williams
>            Priority: Minor
>             Fix For: 1.3.2, 1.4.0
>
>
> While investigating why some recent applications were not showing up in my History Server UI, I found error message blocks like this in the history server logs:
> {code}
> 15/02/12 18:51:55 ERROR scheduler.ReplayListenerBus: Exception in parsing Spark event log.
> java.lang.ClassCastException: org.json4s.JsonAST$JNothing$ cannot be cast to org.json4s.JsonAST$JObject
> 	at org.apache.spark.util.JsonProtocol$.mapFromJson(JsonProtocol.scala:814)
> 	at org.apache.spark.util.JsonProtocol$.executorInfoFromJson(JsonProtocol.scala:805)
> ...
> 	at org.apache.spark.deploy.history.FsHistoryProvider$$anon$1.run(FsHistoryProvider.scala:84)
> 15/02/12 18:51:55 ERROR scheduler.ReplayListenerBus: Malformed line: {"Event":"SparkListenerExecutorAdded","Timestamp":1422897479154,"Executor ID":"12","Executor Info":{"Host":"demeter-csmaz11-1.demeter.hpc.mssm.edu","Total Cores":4}}
> {code}
> Turns out certain files had some malformed lines due to having been generated by a forked Spark with some WIP event-log functionality.
> It would be nice if the first line specified the file the error was found in, and the last line specified the line number.



--
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