sahildevgon opened a new pull request, #22453: URL: https://github.com/apache/kafka/pull/22453
Summary : Whitespace-contaminated min.insync.replicas values silently accepted at write time cause a controller failover loop and full cluster unavailability with no operator-visible warning, because the --describe observability path trims whitespace before displaying the value. Impact A topic config min.insync.replicas stored with leading or trailing whitespace (e.g. " 2") causes the KRaft controller to enter a continuous failover loop, making the cluster unavailable. The crash is triggered on every alterPartition event (e.g. any replica restart), so recovery is not spontaneous. Critically, kafka-topics.sh --describe silently strips the whitespace before displaying the value, so the corrupted config is invisible to operators. There is no log warning, no alert, and no way to detect the problem via the standard Admin API observability path. An operator can stare at a failing cluster and see only clean config values. More Details in JIRA : https://issues.apache.org/jira/browse/KAFKA-20532 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
