Exactly-once semantics (EOS) in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does Exactly-once semantics (EOS) mean in Kafka?

EOS ensures that each message is processed exactly one time, preventing duplicates or data loss even in failures.

intermediate

How does Kafka achieve Exactly-once semantics?

Kafka uses idempotent producers and transactional APIs to guarantee messages are written and processed exactly once.

beginner

What is an idempotent producer in Kafka?

An idempotent producer ensures that resending the same message does not create duplicates, helping EOS.

intermediate

What role do transactions play in Kafka's EOS?

Transactions group multiple writes and commits so they either all succeed or all fail, ensuring atomicity and EOS.

beginner

Why is Exactly-once semantics important in real-world applications?

It prevents duplicate processing or data loss, which is critical for financial systems, order processing, and analytics.

What does Exactly-once semantics guarantee in Kafka?

A Messages can be duplicated but not lost

B Messages can be lost but not duplicated

C Each message is processed only once

D Messages are processed at least once

Exactly-once semantics means each message is processed exactly one time, no duplicates or losses.

Which Kafka feature helps avoid duplicate messages when resending?

A Idempotent producer

B Consumer groups

C Partitioning

D Replication

Idempotent producers ensure resending the same message does not create duplicates.

What does Kafka use to group multiple writes atomically for EOS?

A Transactions

B Partitions

C Offsets

D Consumer commits

Transactions allow grouping writes so they succeed or fail together, ensuring EOS.

Which scenario benefits most from Exactly-once semantics?

A Caching static content

B Financial transaction processing

C Logging debug messages

D Streaming video playback

Financial transactions require no duplicates or losses, so EOS is critical.

If a Kafka producer is not idempotent, what can happen?

A Messages will be lost

B Messages will be compressed

C Messages will be encrypted

D Duplicate messages may be produced

Without idempotency, resending can cause duplicate messages.

Explain how Kafka achieves Exactly-once semantics using idempotent producers and transactions.

Think about how Kafka avoids duplicates and ensures atomic writes.

Why is Exactly-once semantics important in systems like financial applications?

Consider what happens if money is counted twice or lost.

Practice

1. What is the main goal of Exactly-once semantics (EOS) in Kafka?

easy

A. To compress messages for storage efficiency

B. To prevent duplicate or lost messages during data processing

C. To allow multiple consumers to read the same message simultaneously

D. To increase the speed of message delivery

Solution

1. Step 1: Understand the purpose of EOS

   Exactly-once semantics ensures that each message is processed exactly one time, avoiding duplicates or losses.

2. Step 2: Compare options with EOS goal

   Options A, B, and C describe other Kafka features but not EOS's main goal.

3. Final Answer:

   To prevent duplicate or lost messages during data processing -> Option B

4. Quick Check:

   EOS = prevent duplicates/losses [OK]

Hint: EOS means no duplicates or lost messages [OK]

Common Mistakes:

• Confusing EOS with message speed optimization
• Thinking EOS allows multiple consumers to read simultaneously
• Mixing EOS with message compression features

2. Which configuration must be enabled in a Kafka producer to support Exactly-once semantics?

easy

A. max.poll.records = 500

B. acks = 0

C. compression.type = gzip

D. enable.idempotence = true

Solution

1. Step 1: Identify EOS required producer setting

   Enabling idempotence (enable.idempotence = true) is necessary for EOS to avoid duplicates.

2. Step 2: Review other options

   Options B, C, and D relate to acknowledgments, compression, and consumer polling, not EOS.

3. Final Answer:

   enable.idempotence = true -> Option D

4. Quick Check:

   Idempotence enabled = EOS support [OK]

Hint: Enable idempotence for EOS in producer config [OK]

Common Mistakes:

• Setting acks to 0 disables guarantees
• Confusing compression with EOS
• Using consumer settings instead of producer

3. Given the following Kafka producer code snippet with transactions enabled, what will happen if producer.commitTransaction() is not called after producer.send()?

producer.initTransactions();
producer.beginTransaction();
producer.send(record);
// Missing commitTransaction call
producer.close();

medium

A. The transaction will be aborted and messages will not be committed

B. Messages will be committed automatically on close

C. Messages will be duplicated in the topic

D. Producer will throw a syntax error

Solution

1. Step 1: Understand transaction lifecycle in Kafka

   After beginning a transaction and sending messages, commitTransaction() must be called to finalize the transaction.

2. Step 2: Effect of missing commitTransaction()

   If commitTransaction() is not called, the transaction is aborted on close, so messages are not committed.

3. Final Answer:

   The transaction will be aborted and messages will not be committed -> Option A

4. Quick Check:

   Missing commitTransaction = abort transaction [OK]

Hint: Always commit or abort transactions explicitly [OK]

Common Mistakes:

• Assuming close commits automatically
• Expecting duplicates without commit
• Thinking missing commit causes syntax error

4. You have enabled EOS in your Kafka producer but notice duplicate messages in the topic. Which of the following is the most likely cause?

medium

A. Producer did not call initTransactions() before starting transactions

B. Producer set enable.idempotence to true

C. Consumer group is reading messages multiple times

D. Topic has replication factor set to 3

Solution

1. Step 1: Check EOS setup requirements

   initTransactions() must be called before using transactions to ensure EOS works properly.

2. Step 2: Analyze other options

   Producer set enable.idempotence to true is correct config, A relates to consumers not producers, D is unrelated to duplicates.

3. Final Answer:

   Producer did not call initTransactions() before starting transactions -> Option A

4. Quick Check:

   Missing initTransactions() causes duplicates [OK]

Hint: Call initTransactions() before transactions for EOS [OK]

Common Mistakes:

• Confusing consumer behavior with producer duplicates
• Assuming replication factor affects duplicates
• Thinking idempotence alone fixes all issues

5. You want to implement a Kafka producer that writes messages exactly once to multiple partitions atomically. Which combination of settings and steps is required to achieve this?

hard

A. Disable idempotence, send messages asynchronously, then flush producer

B. Set acks=0, send messages to partitions, then close producer

C. Enable idempotence, initialize and begin transactions, send messages, then commit transaction

D. Use synchronous sends without transactions and rely on consumer deduplication

Solution

1. Step 1: Identify EOS requirements for atomic writes

   Enable idempotence and use transactions to ensure atomic writes across partitions.

2. Step 2: Follow correct transaction steps

   Initialize transactions, begin transaction, send messages, then commit transaction to finalize.

3. Step 3: Evaluate other options

   Options B, C, and D lack idempotence or transactions, so they cannot guarantee exactly-once atomic writes.

4. Final Answer:

   Enable idempotence, initialize and begin transactions, send messages, then commit transaction -> Option C

5. Quick Check:

   Idempotence + transactions = atomic exactly-once writes [OK]

Hint: Use idempotence + transactions for atomic exactly-once writes [OK]

Common Mistakes:

• Ignoring transaction lifecycle steps
• Relying on consumer deduplication only
• Disabling idempotence for performance