[jira] [Created] (KAFKA-10060) Kafka is logging too verbosely at the INFO level

["Greg Hamilton (Jira)" <ji...@apache.org>]

Greg Hamilton created KAFKA-10060:
-------------------------------------

             Summary: Kafka is logging too verbosely at the INFO level
                 Key: KAFKA-10060
                 URL: https://issues.apache.org/jira/browse/KAFKA-10060
             Project: Kafka
          Issue Type: Bug
          Components: logging
    Affects Versions: 2.1.0
            Reporter: Greg Hamilton


Some of the INFO level log4j entries are quite verbose and not really useful, for example in kafka.coordinator.group.GroupMetadataManager, the following log can be constantly printed with 0 expired offsets:

 
{code:java}
info(s"Removed $numOffsetsRemoved expired offsets in ${time.milliseconds() - currentTimestamp} milliseconds."){code}
 

 

*Other examples include:*

kafka.coordinator.group.GroupMetadataManager.GroupCoordinator:

 
{code:java}
info(s"Group ${group.groupId} with generation ${group.generationId} is now empty " +            s"(${Topic.GROUP_METADATA_TOPIC_NAME}-${partitionFor(group.groupId)})")
{code}
{code:java}
info(s"Preparing to rebalance group ${group.groupId} in state ${group.currentState} with old generation " +      s"${group.generationId} (${Topic.GROUP_METADATA_TOPIC_NAME}-${partitionFor(group.groupId)}) (reason: $reason)")
{code}
{code:java}
info(s"Assignment received from leader for group ${group.groupId} for generation ${group.generationId}")
{code}
{code:java}
info(s"Stabilized group ${group.groupId} generation ${group.generationId} " + s"(${Topic.GROUP_METADATA_TOPIC_NAME}-${partitionFor(group.groupId)})")
{code}
 

 

We should move them to DEBUG if they are expected in normal state.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)