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/08/01 07:35:04 UTC

[jira] [Commented] (SPARK-6599) Improve usability of Kinesis-based Spark Streaming

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

Tathagata Das commented on SPARK-6599:
--------------------------------------

I am updating the title of this JIRA to better reflect the issue associated with this. In other words, I am reducing the scope this JIRA, and marking it as resolved as all the associated JIRAs are already reasolved in Spark 1.4. For the reliability related issues, please see JIRA - https://issues.apache.org/jira/browse/SPARK-9215

> Improve usability of Kinesis-based Spark Streaming
> --------------------------------------------------
>
>                 Key: SPARK-6599
>                 URL: https://issues.apache.org/jira/browse/SPARK-6599
>             Project: Spark
>          Issue Type: Improvement
>          Components: Streaming
>            Reporter: Tathagata Das
>            Assignee: Tathagata Das
>
> Currently, the KinesisReceiver can loose some data in the case of certain failures (receiver and driver failures). Using the write ahead logs can mitigate some of the problem, but it is not ideal because WALs dont work with S3 (eventually consistency, etc.) which is the most likely file system to be used in the EC2 environment. Hence, we have to take a different approach to improving reliability for Kinesis.
> A detailed design doc on how this can be achieved will be added later.



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