Thank you guys for your response.
That was very helpful. With that in mind, and with some discussions with
the team, we decided to let the application die, so we can monitor and
relaunch it externally.
I think we had something similar to what is described in KAFKA-7970, where
our streams applicatio
Hi Patrik,
Are you referring to the source topic not available or state directory not
available?
For source topic not available case, as Murilo asked about, the main issue
is of the "split brain" case: in very early versions of Kafka, Streams does
check if topics are available at the beginning be
Hi Guozhang
Just a small question, why can't this be checked when trying to instantiate
KafkaStreams?
The Topology should know all topics and the existence of the topics could
be verified with the AdminClient.
This would allow to fail fast similar to when the state directory is not
available.
Or am
Hello Murilo,
Just to give some more background to John's message and KAFKA-7970 here.
The main reason of trickiness is around the scenario of "topics being
partially available", e.g. say your application is joining to topics A and
B, while topicA exists but topicB does not (it is surprisingly com
Hi, Murlio,
I found https://issues.apache.org/jira/browse/KAFKA-7970, which sounds like
the answer is currently "yes". Unfortunately, it is still tricky to handle
this case, although the situation may improve soon.
In the mean time, you can try to work around it with the StateListener.
When Strea
Hi
After some research, I've come to a few discussions, and they all tell me
that Kafka Streams require the topics to be created before starting the
application.
Nevertheless, I'd like my application to keep retrying if a topic does not
exist.
I've seen this thread:
https://groups.google.com/forum/
