Are you suggesting to check the Kafka broker logs? I do not see any other errors logs on the client / application side.
On Fri, 29 Sep, 2023, 22:01 Matthias J. Sax, <mj...@apache.org> wrote: > In general, Kafka Streams should keep running. > > Can you inspect the logs to figure out why it's going into ERROR state > to begin with? Maybe you need to increase/change some timeouts/retries > configs. > > The stack trace you shared, is a symptom, but not the root cause. > > -Matthias > > On 9/21/23 12:56 AM, Debraj Manna wrote: > > I am using Kafka broker 2.8.1 (from AWS MSK) with Kafka clients and Kafka > > stream 3.5.1. > > > > I am observing that whenever some rolling upgrade is done on AWS MSK our > > stream application reaches an error state. I get the below exception on > > trying to query the state store > > > > caused by: java.lang.IllegalStateException: KafkaStreams is not running. > > State is ERROR. > > at > > > org.apache.kafka.streams.KafkaStreams.validateIsRunningOrRebalancing(KafkaStreams.java:381) > > at > > > org.apache.kafka.streams.KafkaStreams.queryMetadataForKey(KafkaStreams.java:1663) > > at > > > org.springframework.cloud.stream.binder.kafka.streams.InteractiveQueryService.lambda$getHostInfo$2(InteractiveQueryService.java:227) > > > > Can someone let me know what the recommended way we can keep the stream > > application running whenever some rolling upgrade/restart of brokers is > > done in the background? > > >
