Bird
0
0

In a Kafka cluster, a broker is down and some partitions have no leader. What is a common cause?

medium📝 Debug Q7 of 15
Kafka - Cluster Architecture
In a Kafka cluster, a broker is down and some partitions have no leader. What is a common cause?
AReplication factor set to 1
BToo many brokers available
CInsufficient in-sync replicas to elect a new leader
DTopic has zero partitions
Step-by-Step Solution
Solution:

  1. Step 1: Understand leader election in Kafka

    Leaders are elected from in-sync replicas (ISRs).

  2. Step 2: Analyze broker down effect

    If ISRs are insufficient, no leader can be elected for partitions.

  3. Final Answer:

    Insufficient in-sync replicas to elect a new leader -> Option C

  4. Quick Check:

    Leader election needs enough ISRs [OK]
Quick Trick: Leader election requires enough in-sync replicas [OK]
Common Mistakes:
  • Ignoring ISR count
  • Thinking replication factor 1 causes leader loss
  • Assuming too many brokers cause this

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Rebalancing behavior - Quiz 1easy Consumer Groups - Partition assignment - Quiz 4medium Consumer Groups - Group coordinator - Quiz 4medium Consumers - Auto-commit vs manual commit - Quiz 9hard Kafka Basics and Event Streaming - Why Kafka exists - Quiz 13medium Producers - Compression (gzip, snappy, lz4) - Quiz 15hard Producers - Why producers publish data - Quiz 7medium Topics and Partitions - Topic creation - Quiz 6medium Topics and Partitions - Partition key and routing - Quiz 1easy Topics and Partitions - Why topics organize messages - Quiz 2easy