[
https://issues.apache.org/jira/browse/SPARK-18983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-18983.
-------------------------------
Resolution: Invalid
Target Version/s: (was: 1.6.1)
Please read http://spark.apache.org/contributing.html
This should go to [email protected]
But if all your brokers are down, this is the behavior you expect.
> Couldn't find leader offsets exception when the one of kafka cluster brokers
> is down
> ------------------------------------------------------------------------------------
>
> Key: SPARK-18983
> URL: https://issues.apache.org/jira/browse/SPARK-18983
> Project: Spark
> Issue Type: Bug
> Reporter: kraken
> Priority: Critical
>
> Hello,i got a trouble today
> when the company's PE restarts the one of kafka cluster broker,my spark job
> run failed.
> Exception in thread "main" org.apache.spark.SparkException: get earliest
> leader offsets failed: ArrayBuffer(org.apache.spark.SparkException: Couldn't
> find leaders for Set
> I use the low level type to consume kafka log, i know that high level can be
> aware of the lead changes, but how can i do that by use low level?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
