Bird
0
0

A Kafka producer is configured with acks=all but messages are still lost during broker failure. What could be a possible cause?

medium📝 Debug Q7 of 15
Kafka - Producers
A Kafka producer is configured with acks=all but messages are still lost during broker failure. What could be a possible cause?
AThe producer is using <code>acks=0</code> internally.
BThe topic has only one partition.
CThe producer retries are disabled.
DThe <code>min.insync.replicas</code> setting is too low or not configured properly.
Step-by-Step Solution
Solution:

  1. Step 1: Understand acks=all guarantees

    acks=all waits for all in-sync replicas to confirm, but depends on min.insync.replicas.

  2. Step 2: Identify cause of message loss

    If min.insync.replicas is low or misconfigured, fewer replicas confirm, risking data loss on failure.

  3. Final Answer:

    The min.insync.replicas setting is too low or not configured properly. -> Option D

  4. Quick Check:

    min.insync.replicas controls replication safety with acks=all [OK]
Quick Trick: Check min.insync.replicas when using acks=all [OK]
Common Mistakes:
  • Assuming acks=all alone guarantees no loss
  • Ignoring min.insync.replicas importance
  • Blaming producer retries for replication loss

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Cooperative vs eager rebalancing - Quiz 10hard Consumer Groups - Group coordinator - Quiz 3easy Consumer Groups - Rebalancing behavior - Quiz 10hard Consumers - Auto-commit vs manual commit - Quiz 11easy Kafka Cluster Architecture - Controller broker - Quiz 10hard Producers - Partitioner behavior - Quiz 14medium Topics and Partitions - Why topics organize messages - Quiz 8hard Topics and Partitions - Partition concept - Quiz 7medium Topics and Partitions - Retention policies (time-based, size-based) - Quiz 14medium Topics and Partitions - Retention policies (time-based, size-based) - Quiz 12easy