You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/12/22 19:07:58 UTC

[jira] [Resolved] (SPARK-18982) Couldn't find leader offsets exception when the one of kafka cluster brokers is down

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

Sean Owen resolved SPARK-18982.
-------------------------------
          Resolution: Duplicate
    Target Version/s:   (was: 1.6.1)

> Couldn't find leader offsets exception when the one of kafka cluster brokers is down
> ------------------------------------------------------------------------------------
>
>                 Key: SPARK-18982
>                 URL: https://issues.apache.org/jira/browse/SPARK-18982
>             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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org