Exactly-once semantics (EOS) in Kafka - Step-by-Step Execution

Process Flow - Exactly-once semantics (EOS)

Start Producer

↓

Begin Transaction

↓

Send Messages

↓

Commit Transaction

↓

Broker stores messages atomically

↓

Consumer reads messages once

↓

End

The producer starts a transaction, sends messages, commits atomically, ensuring messages are stored and consumed exactly once.

Execution Sample

Kafka

producer.initTransactions();
producer.beginTransaction();
producer.send(record1);
producer.send(record2);
producer.commitTransaction();

This code shows a Kafka producer sending two messages within a transaction to guarantee exactly-once delivery.

Process Table

Step	Action	State Change	Result
1	Initialize transactions	Producer ready for transactions	No messages sent yet
2	Begin transaction	Transaction started	Messages will be sent atomically
3	Send record1	Record1 buffered in transaction	Not visible to consumers yet
4	Send record2	Record2 buffered in transaction	Not visible to consumers yet
5	Commit transaction	Transaction committed atomically	Both records become visible exactly once
6	Consumer reads messages	Reads record1 and record2 once	No duplicates or missing messages
7	End	Transaction complete	Exactly-once semantics ensured

💡 Transaction committed, messages stored atomically, ensuring exactly-once delivery

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
transactionState	none	started	started	started	committed	committed
bufferedMessages	[]	[]	[record1]	[record1, record2]	[]	[]
messagesVisibleToConsumer	[]	[]	[]	[]	[record1, record2]	[record1, record2]

Key Moments - 3 Insights

Why are messages not visible to consumers before commit?

Because messages are buffered in the transaction (see steps 3 and 4 in execution_table), they become visible only after commit (step 5), ensuring atomic visibility.

What happens if the transaction is aborted instead of committed?

If aborted, buffered messages are discarded and never become visible, preventing duplicates or partial writes (not shown in this trace but important for EOS).

How does exactly-once semantics prevent duplicates?

By committing messages atomically and tracking offsets, Kafka ensures consumers read each message once after commit (step 6), avoiding duplicates.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of bufferedMessages after step 4?

A []

B [record1]

C [record1, record2]

D [record2]

💡 Hint

Check the 'bufferedMessages' variable in variable_tracker after step 4

At which step do messages become visible to consumers?

A Step 3

B Step 5

C Step 2

D Step 4

💡 Hint

Look at 'messagesVisibleToConsumer' in variable_tracker and execution_table rows

If the transaction was aborted instead of committed at step 5, what would happen to bufferedMessages?

A They would be discarded and not sent

B They would be sent to consumers immediately

C They would remain buffered indefinitely

D They would be duplicated

💡 Hint

Recall the explanation in key_moments about aborting transactions

Concept Snapshot

Exactly-once semantics (EOS) in Kafka:
- Producer starts a transaction
- Sends messages buffered in transaction
- Commits transaction atomically
- Messages become visible once committed
- Consumers read messages exactly once
- Prevents duplicates and data loss

Full Transcript

Exactly-once semantics (EOS) in Kafka means messages are sent and stored so that consumers see each message only once. The producer starts a transaction, sends messages buffered inside it, and commits the transaction atomically. Before commit, messages are not visible to consumers. After commit, all messages become visible together. This prevents duplicates and partial writes. If the transaction aborts, messages are discarded. Consumers read committed messages exactly once, ensuring reliable processing.

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