You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "yangping wu (JIRA)" <ji...@apache.org> on 2015/06/17 04:07:00 UTC

[jira] [Comment Edited] (SPARK-6892) Recovery from checkpoint will also reuse the application id when write eventLog in yarn-cluster mode

    [ https://issues.apache.org/jira/browse/SPARK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589180#comment-14589180 ] 

yangping wu edited comment on SPARK-6892 at 6/17/15 2:06 AM:
-------------------------------------------------------------

Hi [~hshreedharan], We can set *spark.eventLog.overwrite* to true to solve this problem. And this issue can be closed. Thank you.


was (Author: 397090770):
Hi [~hshreedharan], We can set *spark.eventLog.overwrite* to true to solve this problem.

> Recovery from checkpoint will also reuse the application id when write eventLog in yarn-cluster mode
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-6892
>                 URL: https://issues.apache.org/jira/browse/SPARK-6892
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.3.0
>            Reporter: yangping wu
>            Priority: Critical
>
> When I recovery from checkpoint  in yarn-cluster mode using Spark Streaming,  I found it will reuse the application id (In my case is application_1428664056212_0016) before falied to write spark eventLog, But now my application id is application_1428664056212_0017,then spark write eventLog will falied, the stacktrace as follow:
> {code}
> 15/04/14 10:14:01 WARN util.ShutdownHookManager: ShutdownHook '$anon$3' failed, java.io.IOException: Target log file already exists (hdfs://mycluster/spark-logs/eventLog/application_1428664056212_0016)
> java.io.IOException: Target log file already exists (hdfs://mycluster/spark-logs/eventLog/application_1428664056212_0016)
> 	at org.apache.spark.scheduler.EventLoggingListener.stop(EventLoggingListener.scala:201)
> 	at org.apache.spark.SparkContext$$anonfun$stop$4.apply(SparkContext.scala:1388)
> 	at org.apache.spark.SparkContext$$anonfun$stop$4.apply(SparkContext.scala:1388)
> 	at scala.Option.foreach(Option.scala:236)
> 	at org.apache.spark.SparkContext.stop(SparkContext.scala:1388)
> 	at org.apache.spark.deploy.yarn.ApplicationMaster$$anon$3.run(ApplicationMaster.scala:107)
> 	at org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
> {code}
> This exception will cause the job falied.



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