Ryan Williams created SPARK-5783:
------------------------------------
Summary: 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.2.1
Reporter: Ryan Williams
Priority: Minor
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: [email protected]
For additional commands, e-mail: [email protected]
