Hi Misha,
If it works locally, then I would still suspect that it is due to a
transient timing issue: note that the create-topic script is non-blocking,
i.e. even when it returns it does not necessarily guarantee that the leader
metadata information has been completed propagating to brokers.
Thanks Guozhang,
Yes, I rely on auto-create, and it works locally. Maybe I need to tweak some
timeout conf for that?
Also I identified, that even I manually create a topic, it lists but I can not
produce messages to this topic with the same exception.
Producing to other topics works well, so
Misha,
Did you pre-create the sink topic before starting your application or you
are relying on the broker-side auto-create for that topic?
If you are relying on auto-create, then there is a transient period where
the topic is created but the metadata has not been propagated to the
brokers so
Hello,
I’ve a simplest ever kafka streams application which just reads from one kafka
topic A and write to another topic B.
When I run it on my local environment (local zk, local kafka broker, local
kafka streams app) everything works fine, topic B created and filled with
messages from A
If I
