Hi Daan,
First of all, it does sound like that is a correct
implementation of QueryableStoreProvider. Kudos for taking
that on; the complexity of that API was one of my top
motivations for replacing it with IQv2!
(https://cwiki.apache.org/confluence/display/KAFKA/KIP-796%3A+Interactive+Query+v2
)
It is correct, that Kafka Streams does not create input/output/through()
topics. You should create those topics upfront.
> We've *set auto.create.topics.enable=true *in our kafka
>> server properties file and we'd expect that the topics get created, but the
>> consumer goes into SHUTDOWN mode and
After adding more logging details, we found that we hadn't created topics
yet for the consumer & producer for the streams application. We've added a
check when starting up to verify that the topics exist, otherwise we exit
our app. We're not dynamically creating topics and we want to create them
up
Does the application transit to RUNNING state? Also check
`KafkaStreams#localThreadsMetadata()` what tasks are assigned?
You might also enable DEBUG logs for
`org.apache.kafka.clients.consumer.**` classes to see if the consumer
sends fetch request to the broker.
-Matthias
On 6/11/19 7:03 PM, Br
The application just hangs (we let it sit for ~1 hour, small dataset as
we're testing), we can restart it listening to 1 of the 3 topics we start
it with and it chugs along, no problem. The same code is executed as
separate application.ids listening to other topics without any issues.
We'll try to
What do you exactly observe?
- Does the application rebalance correctly?
- Does it start processing?
- Anything in the logs about the status of the application?
-Matthias
On 6/10/19 6:19 PM, Brian Putt wrote:
> Hello,
>
> I'm working with the kafka streams api and am running into issues whe
