A topic 'recurring payments' is created on a Kafka cluster with three brokers (broker id '0', '1', '2') and nine partitions. The 'min.insync replicas' is set to three, and producer is set with…

Question

Options

• AConsumers can read committed messages from partitions on broker id '1', '2'.
• BProducers can write messages to all the partitions, because new leaders for the partitions will be
• CProducers and consumers will have no impact on six of the nine partitions.
• DProducers will only be able to write messages to the topic where the Leader for the partition is on

• A
  2% (1)
• B
  4% (2)
• C
  83% (43)
• D
  12% (6)

Explanation

With 9 partitions spread across 3 brokers, each broker typically hosts 3 leaders (assuming even distribution). When Broker 0 fails, the partitions for which it was leader will elect new leaders on brokers 1 or 2 if enough in-sync replicas (ISRs) remain. But since min.insync.replicas=3 and only 2 brokers are up, no partition can meet the minimum in-sync replica requirement, so producers with acks=all will fail to write. However, for partitions where Broker 0 is not the leader, consumers can still read committed messages. Given that only 3 partitions likely had Broker 0 as leader, six partitions remain accessible for reads, but not writes.

No community discussion yet for this question.