You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Tathagata Das (JIRA)" <ji...@apache.org> on 2015/09/12 02:53:46 UTC
[jira] [Commented] (SPARK-7942) Receiver's life cycle is
inconsistent with streaming job.
[ https://issues.apache.org/jira/browse/SPARK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741800#comment-14741800 ]
Tathagata Das commented on SPARK-7942:
--------------------------------------
This has been resolved in Spark 1.5.0 where we reimplemented the receiver scheduling to keep relaunching and not be limited by the max task retries
> Receiver's life cycle is inconsistent with streaming job.
> ---------------------------------------------------------
>
> Key: SPARK-7942
> URL: https://issues.apache.org/jira/browse/SPARK-7942
> Project: Spark
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.4.0
> Reporter: SaintBacchus
>
> Streaming consider the receiver as a common spark job, thus if an error occurs in the receiver's logical(after 4 times(default) retries ), streaming will no longer get any data but the streaming job is still running.
> A general scenario is that: we config the `spark.streaming.receiver.writeAheadLog.enable` as true to use the `ReliableKafkaReceiver` but do not set the checkpoint dir. Then the receiver will soon be shut down but the streaming is alive.
--
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