Matthias
It happened again yesterday during another rolling update. The first error
log I can see on the client side is below. It was there in PENDING_ERROR
state for sometime and then went into ERROR state.
Caused by: java.lang.IllegalStateException: KafkaStreams is not running.
State is
I did mean client side... If KS goes into ERROR state, it should log
the reason.
If the logs are indeed empty, try to register an
uncaught-exception-handler via
KafkaStreamssetUncaughtExceptionHandler(...)
-Matthias
On 10/2/23 12:11 PM, Debraj Manna wrote:
Are you suggesting to check
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, wrote:
> In general, Kafka Streams should keep running.
>
> Can you inspect the logs to figure out why it's going into ERROR state
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
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:
