spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yue long (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-21836) [STREAMING] Retry when kafka broker is down in kafka-streaming
Date Fri, 25 Aug 2017 08:26:00 GMT

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

yue long updated SPARK-21836:
-----------------------------
    Description: 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
 

> [STREAMING] Retry when kafka broker is down in kafka-streaming
> --------------------------------------------------------------
>
>                 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


Mime
View raw message