Kafka under-replicated partitions

Jacob Lionel 0 Reputation points
2026-09-18T14:02:21.44+00:00

Apache Kafka cluster throwing under-replicated partition alert following broker node reboot. How to trigger partition reassignment?

Windows for business | Windows Server | Storage high availability | Clustering and high availability
0 comments No comments

1 answer

Sort by: Newest
  1. Hoang Le 6,030 Reputation points Independent Advisor
    2026-09-18T14:37:28.01+00:00

    Hello Jacob Lionel,

    In a Kafka cluster, the “under‑replicated partitions” alert after a broker reboot means that replicas are not fully synchronized with the leader. To trigger a reassignment, you use the Kafka partition reassignment tool. First, generate a reassignment plan with kafka-reassign-partitions.sh --generate --zookeeper zkhost:2181 --topics-to-move-json-file topics.json --broker-list <brokerIDs> --output-reassignment-json-file reassignment.json. Then execute it with kafka-reassign-partitions.sh --execute --zookeeper zkhost:2181 --reassignment-json-file reassignment.json. This forces Kafka to redistribute replicas across the specified brokers. You can verify progress with the same script using --verify. On newer versions, the Admin API or kafka-topics.sh --alter can be used instead, but the principle is the same: explicitly instruct the cluster to rebalance replicas. Always confirm that unclean.leader.election.enable is set appropriately to avoid data loss during leader re‑elections.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    HL.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.