Skip to content

Adding --ignore-formatted for kafka-storage.sh to work with < 4.0 kafka when additional disks are added #234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cawright-rh merged 1 commit into from
Feb 18, 2026
Merged

Adding --ignore-formatted for kafka-storage.sh to work with < 4.0 kafka when additional disks are added #234

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pkg/resources/kafka/wait-for-envoy-sidecar.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ if [[ -n "${CLUSTER_ID}" ]]; then
# If the storage is already formatted (e.g. broker restarts), the kafka-storage.sh will skip formatting for that storage
# thus we can safely run the storage format command regardless if the storage has been formatted or not
echo "Formatting KRaft storage with cluster ID ${CLUSTER_ID}"
/opt/kafka/bin/kafka-storage.sh format --cluster-id "${CLUSTER_ID}" -c /config/broker-config
/opt/kafka/bin/kafka-storage.sh format --cluster-id "${CLUSTER_ID}" --ignore-formatted -c /config/broker-config

# Adding or removing controller nodes to the Kafka cluster would trigger cluster rolling upgrade so all the nodes in the cluster are aware of the newly added/removed controllers.
# When this happens, Kafka's local quorum state file would be outdated since it is static and the Kafka server can't be started with conflicting controllers info (compared to info stored in ConfigMap),
Expand Down