You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Glen Mazza (Jira)" <ji...@apache.org> on 2025/11/10 16:11:00 UTC

[jira] [Created] (ZOOKEEPER-4993) Lower "Attempting to delete candidate container..." logging to DEBUG

Glen Mazza created ZOOKEEPER-4993:
-------------------------------------

             Summary: Lower "Attempting to delete candidate container..." logging to DEBUG
                 Key: ZOOKEEPER-4993
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4993
             Project: ZooKeeper
          Issue Type: Task
          Components: server
            Reporter: Glen Mazza


[https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/ContainerManager.java#L134]

Can we get the "Attempting to delete candidate container..." logging statement lowered from INFO to DEBUG?  We're getting about 2.0+ million of these logging statements each day (no exaggeration, actually).

If we raised our logging for this class to WARN, to avoid the above statement, we'd miss the LOG.info("Using checkIntervalMs={} maxPerMinute={} maxNeverUsedIntervalMs={}" statement in the Constructor that we'd like to keep.

Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)