diff --git a/config/log4j2.yaml b/config/log4j2.yaml
index 49bcf78d136..de263c57c92 100644
--- a/config/log4j2.yaml
+++ b/config/log4j2.yaml
@@ -44,7 +44,7 @@ Configuration:
# State Change appender
- name: StateChangeAppender
fileName: "${sys:kafka.logs.dir}/state-change.log"
- filePattern: "${sys:kafka.logs.dir}/stage-change.log.%d{yyyy-MM-dd-HH}"
+ filePattern: "${sys:kafka.logs.dir}/state-change.log.%d{yyyy-MM-dd-HH}"
PatternLayout:
pattern: "${logPattern}"
TimeBasedTriggeringPolicy:
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 7381347a6b6..ac32d983e88 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -57,6 +57,9 @@
The logger class name for LogCleaner has been updated from kafka.log.LogCleaner to org.apache.kafka.storage.internals.log.LogCleaner in the log4j2.yaml configuration file.
Added loggers for org.apache.kafka.storage.internals.log.LogCleaner$CleanerThread and org.apache.kafka.storage.internals.log.Cleaner classes to CleanerAppender.
+
state-change.log files has been updated from stage-change.log.[date] to state-change.log.[date] in the log4j2.yaml configuration file.
+ For a rolling upgrade:
@@ -117,7 +120,7 @@ or KIP-1124. -Note: Apache Kafka 4.0 only supports KRaft mode - ZooKeeper mode has been removed. As such, broker upgrades to 4.0.0 (and higher) require KRaft mode and
the software and metadata versions must be at least 3.3.x (the first version when KRaft mode was deemed production ready). For clusters in KRaft mode
@@ -141,7 +144,13 @@
has a boolean parameter that indicates if there are metadata changes (i.e. IBP_4_0_IV1(23, "4.0", "IV1", true) means this version has metadata changes).
Given your current and target versions, a downgrade is only possible if there are no metadata changes in the versions between.
-
+
state-change.log files has been updated from stage-change.log.[date] to state-change.log.[date] in the log4j2.yaml configuration file.
+ See KAFKA-19576 for details.
+ state-change.log files incorrectly rotates to stage-change.log.[date] (changing state to stage). This issue is corrected in 4.0.1.
+ See KAFKA-19576 for details.
+