From 6ef675d08b346e5f1e6d3a33a91faad18d608d43 Mon Sep 17 00:00:00 2001
From: Sushant Mahajan <smahajan@confluent.io>
Date: Mon, 21 Jul 2025 20:43:37 +0530
Subject: [PATCH] MINOR: Change log level for cold snapshot log. (#20209)

* We INFO log a message, if a share partition could be cold snapshotted.
* However, this may create noise if we have highly partitioned topic
backing the share partition. This will be further exacerbated by
multiple share groups using that topic.
* To reduce log pollution, this PR changes the level to DEBUG.

Reviewers: ShivsundarR <shr@confluent.io>, Andrew Schofield
 <aschofield@confluent.io>
---
 .../apache/kafka/coordinator/share/ShareCoordinatorShard.java   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/share-coordinator/src/main/java/org/apache/kafka/coordinator/share/ShareCoordinatorShard.java b/share-coordinator/src/main/java/org/apache/kafka/coordinator/share/ShareCoordinatorShard.java
index 5dad56f48bc..76a654de4c1 100644
--- a/share-coordinator/src/main/java/org/apache/kafka/coordinator/share/ShareCoordinatorShard.java
+++ b/share-coordinator/src/main/java/org/apache/kafka/coordinator/share/ShareCoordinatorShard.java
@@ -593,7 +593,7 @@ public class ShareCoordinatorShard implements CoordinatorShard<CoordinatorRecord
             long timeSinceLastSnapshot = time.milliseconds() - shareGroupOffset.writeTimestamp();
             if (timeSinceLastSnapshot >= config.shareCoordinatorColdPartitionSnapshotIntervalMs()) {
                 // We need to force create a snapshot here
-                log.info("Last snapshot for {} is older than allowed interval.", sharePartitionKey);
+                log.debug("Last snapshot for {} is older than allowed interval (last snapshot delta {}).", sharePartitionKey, timeSinceLastSnapshot);
                 records.add(ShareCoordinatorRecordHelpers.newShareSnapshotRecord(
                     sharePartitionKey.groupId(),
                     sharePartitionKey.topicId(),