[KAFKA-17148] Kafka storage tool prints MetaPropertiesEnsemble

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.7.0, 3.8.0, 3.7.1
• Fix Version/s: 3.8.0, 3.9.0, 3.7.2
• Labels: newbie
• Assignee: Dmitry Werner
• Reporter: Greg Harris
• Created: 16/Jul/24 19:06
• Updated: 18/Jul/24 00:13
• Resolved: 17/Jul/24 15:16

Description

Using this following command on the 3.6 branch yields this result:

$ bin/kafka-storage.sh format --config config/kraft/server.properties --cluster-id "$(bin/kafka-storage.sh random-uuid)"
Formatting /tmp/kraft-combined-logs with metadata.version 3.6-IV2.

While on 3.7 it has this behavior:

$ bin/kafka-storage.sh format --config config/kraft/server.properties --cluster-id "$(bin/kafka-storage.sh random-uuid)"
SLF4J: Class path contains multiple SLF4J bindings.
...
SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]
metaPropertiesEnsemble=MetaPropertiesEnsemble(metadataLogDir=Optional.empty, dirs={/tmp/kraft-combined-logs: EMPTY})
Formatting /tmp/kraft-combined-logs with metadata.version 3.7-IV4.

and on 3.8:

$ bin/kafka-storage.sh format --config config/kraft/server.properties --cluster-id "$(bin/kafka-storage.sh random-uuid)"
metaPropertiesEnsemble=MetaPropertiesEnsemble(metadataLogDir=Optional.empty, dirs={/tmp/kraft-combined-logs: EMPTY})
Formatting /tmp/kraft-combined-logs with metadata.version 3.8-IV0.

This doesn't appear to be a useful log message for users, so could/should be eliminated.

Issue Links

• links to: GitHub Pull Request #16607
• links to: GitHub Pull Request #16616
• links to: GitHub Pull Request #16617