You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2017/02/07 22:51:41 UTC
[jira] [Comment Edited] (KAFKA-4564) When the destination brokers
are down or misconfigured in config, Streams should fail fast
[ https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856964#comment-15856964 ]
Gwen Shapira edited comment on KAFKA-4564 at 2/7/17 10:51 PM:
--------------------------------------------------------------
OMG, this is great. I got this:
{code}
[2017-02-07 14:48:10,250] INFO Deleting obsolete state directory 0_0 for task 0_0 as cleanup delay of 0 ms has passed (org.apache.kafka.streams.processor.internals.StateDirectory)
Exception in thread "main" org.apache.kafka.streams.errors.StreamsException: Could not find any available broker.
at org.apache.kafka.streams.processor.internals.StreamsKafkaClient.getBrokerId(StreamsKafkaClient.java:205)
at org.apache.kafka.streams.processor.internals.StreamsKafkaClient.checkBrokerCompatibility(StreamsKafkaClient.java:266)
at org.apache.kafka.streams.KafkaStreams.checkBrokerVersionCompatibility(KafkaStreams.java:392)
at org.apache.kafka.streams.KafkaStreams.start(KafkaStreams.java:416)
at com.shapira.examples.streams.stockstats.StockStatsExample.main(StockStatsExample.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
{code}
It took about a minute to get it though. Is this timeout tunable?
was (Author: gwenshap):
OMG, this is great. I got this:
````
[2017-02-07 14:48:10,250] INFO Deleting obsolete state directory 0_0 for task 0_0 as cleanup delay of 0 ms has passed (org.apache.kafka.streams.processor.internals.StateDirectory)
Exception in thread "main" org.apache.kafka.streams.errors.StreamsException: Could not find any available broker.
at org.apache.kafka.streams.processor.internals.StreamsKafkaClient.getBrokerId(StreamsKafkaClient.java:205)
at org.apache.kafka.streams.processor.internals.StreamsKafkaClient.checkBrokerCompatibility(StreamsKafkaClient.java:266)
at org.apache.kafka.streams.KafkaStreams.checkBrokerVersionCompatibility(KafkaStreams.java:392)
at org.apache.kafka.streams.KafkaStreams.start(KafkaStreams.java:416)
at com.shapira.examples.streams.stockstats.StockStatsExample.main(StockStatsExample.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
````
It took about a minute to get it though. Is this timeout tunable?
> When the destination brokers are down or misconfigured in config, Streams should fail fast
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-4564
> URL: https://issues.apache.org/jira/browse/KAFKA-4564
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Umesh Chaudhary
> Labels: newbie
>
> Today if Kafka is down or users misconfigure the bootstrap list, Streams may just hangs for a while without any error messages even with the log4j enabled, which is quite confusing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)