...

• Users that have a large amount of topics in a single cluster, making it incredibly hard to manually repartition all topics that have under-replicated partitions, so they only take action when it hits CRITICAL state
• Users with a high replication-factor that can tolerate some broker failures and only take action when it hits CRITICAL state

My group is currently one of these cases and we created a script to periodically run the describe-topics command and extract any CRITICAL topic partitions from the output to alert us.

Public Interfaces

This change would only modify kafka-topics.sh script to include an additional option that follows the existing output of the under-replicated-partitions and offline-partitions options.

...