[KAFKA-10060] Kafka is logging too verbosely at the INFO level

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: logging
• Assignee: Unassigned
• Reporter: Greg Hamilton
• Created: 28/May/20 18:27
• Updated: 31/May/20 21:59

Description

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:

 

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

 

 

Other examples include:

kafka.coordinator.group.GroupMetadataManager.GroupCoordinator:

 

info(s"Group ${group.groupId} with generation ${group.generationId} is now empty " +            s"(${Topic.GROUP_METADATA_TOPIC_NAME}-${partitionFor(group.groupId)})")

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)")

info(s"Assignment received from leader for group ${group.groupId} for generation ${group.generationId}")

info(s"Stabilized group ${group.groupId} generation ${group.generationId} " + s"(${Topic.GROUP_METADATA_TOPIC_NAME}-${partitionFor(group.groupId)})")

 

 

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

Issue Links

• relates to: KAFKA-1592 Some INFO level logging needs to be DEBUG
• links to: GitHub Pull Request #8767