You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "yue long (JIRA)" <ji...@apache.org> on 2017/08/25 08:26:00 UTC

[jira] [Updated] (SPARK-21836) [STREAMING] Retry when kafka broker is down in kafka-streaming-0-8

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

yue long updated SPARK-21836:
-----------------------------
    Summary: [STREAMING] Retry when kafka broker is down in kafka-streaming-0-8  (was: [STREAMING] Retry when kafka broker is down in kafka-streaming)

> [STREAMING] Retry when kafka broker is down in kafka-streaming-0-8
> ------------------------------------------------------------------
>
>                 Key: SPARK-21836
>                 URL: https://issues.apache.org/jira/browse/SPARK-21836
>             Project: Spark
>          Issue Type: Improvement
>          Components: DStreams
>    Affects Versions: 1.6.3, 2.1.0
>            Reporter: yue long
>
> When using the package spark-streaming-kafka-0-8 for accessing kafka in spark dstream, many user will face the "could not find leader" exception if some of kafka brokers are down. This will cause the whole streaming fail. Like  [SPARK-18983|https://issues.apache.org/jira/browse/SPARK-18983] said. The failed kafka brokers may also cause other problems like creating Dstream or creating  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org