a-dudko commented on PR #12875:
URL: https://github.com/apache/kafka/pull/12875#issuecomment-2996565101
We are using version 3.9.1 now and we see plenty of the logs like
`stream-thread [service-e7c3de52-cf29-49c3-8f9d-1eea119ea532-StreamThread-1]
Encountered lock exception. Reattempting locking the state in the next
iteration.`
with the following stacktrace
`org.apache.kafka.streams.errors.LockException: stream-thread
[service-e7c3de52-cf29-49c3-8f9d-1eea119ea532-StreamThread-1] task [1_42]
Failed to lock the state directory for task 1_42
at
org.apache.kafka.streams.processor.internals.StateManagerUtil.registerStateStores(StateManagerUtil.java:97)
at
org.apache.kafka.streams.processor.internals.StreamTask.initializeIfNeeded(StreamTask.java:266)
at
org.apache.kafka.streams.processor.internals.TaskManager.addTaskToStateUpdater(TaskManager.java:1016)
at
org.apache.kafka.streams.processor.internals.TaskManager.addTasksToStateUpdater(TaskManager.java:1001)
at
org.apache.kafka.streams.processor.internals.TaskManager.checkStateUpdater(TaskManager.java:915)
at
org.apache.kafka.streams.processor.internals.StreamThread.checkStateUpdater(StreamThread.java:1191)
at
org.apache.kafka.streams.processor.internals.StreamThread.runOnceWithoutProcessingThreads(StreamThread.java:999)
at
org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:713)
at
org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:672)`
which is kind of fine I assume also given the log level INFO
But they are eventually followed by an ERROR like
`stream-thread [service-e7c3de52-cf29-49c3-8f9d-1eea119ea532-StreamThread-1]
standby-task [1_42] Failed to acquire lock while closing the state store for
STANDBY task 1_42`
Are we missing some other fix or is there smth wrong with the config on our
side?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
