From 9682e63c11447d7448db00fd6477fd00a9ace327 Mon Sep 17 00:00:00 2001 From: Danica Fine Date: Wed, 13 Nov 2024 03:32:40 -0800 Subject: [PATCH] KAFKA-17109: Reduce log message load for failed locking (#16705) Reducing log messaging by removing stacktrace. Reviewer: Bruno Cadonna --- .../apache/kafka/streams/processor/internals/TaskManager.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java b/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java index 8a6e27b4c9944..f361d3dc32011 100644 --- a/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java +++ b/streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java @@ -1076,7 +1076,8 @@ private void addTaskToStateUpdater(final Task task) { } catch (final LockException lockException) { // The state directory may still be locked by another thread, when the rebalance just happened. // Retry in the next iteration. - log.info("Encountered lock exception. Reattempting locking the state in the next iteration.", lockException); + log.info("Encountered lock exception. Reattempting locking the state in the next iteration. Error message was: {}", + lockException.getMessage()); tasks.addPendingTasksToInit(Collections.singleton(task)); updateOrCreateBackoffRecord(task.id(), nowMs); }