Exactly-once semantics (EOS) in Kafka - Mini Project: Build & Apply

Exactly-once semantics (EOS) with Kafka Producer

📖 Scenario: You are building a simple Kafka producer application that sends messages to a Kafka topic. To ensure data integrity, you want to guarantee that each message is delivered exactly once, even if retries happen due to network issues.

🎯 Goal: Create a Kafka producer configuration that enables exactly-once semantics (EOS) and send a few messages to a Kafka topic named eos_topic.

📋 What You'll Learn

Create a Kafka producer configuration with enable.idempotence set to true

Set a transactional.id to enable transactions

Initialize transactions before sending messages

Send three messages to the topic eos_topic within a transaction

Commit the transaction to ensure exactly-once delivery

Print a confirmation message after successful commit

💡 Why This Matters

🌍 Real World

Exactly-once semantics are critical in financial systems, order processing, and any application where duplicate messages can cause errors or inconsistencies.

💼 Career

Kafka developers and data engineers often need to implement EOS to guarantee data integrity in distributed streaming applications.

1

Create Kafka producer configuration with EOS settings

Create a dictionary called producer_config with these exact entries: 'bootstrap.servers': 'localhost:9092', 'enable.idempotence': True, and 'transactional.id': 'my-transactional-id'.

Kafka

# Create the Kafka producer configuration dictionary
# Your code here

Hint

Use a Python dictionary with the exact keys and values as specified.

2

Initialize Kafka producer and transactions

Import Producer from confluent_kafka. Create a Producer instance called producer using producer_config. Then call producer.init_transactions() to initialize transactions.

Kafka

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'enable.idempotence': True,
    'transactional.id': 'my-transactional-id'
}

# Import Producer and create producer instance
# Initialize transactions
# Your code here

Hint

Remember to import Producer and call init_transactions() on the producer instance.

3

Send messages within a transaction

Use producer.begin_transaction() to start a transaction. Then send three messages with keys 'key1', 'key2', 'key3' and values 'message1', 'message2', 'message3' respectively to the topic 'eos_topic' using producer.produce(). Finally, call producer.commit_transaction() to commit the transaction.

Kafka

from confluent_kafka import Producer

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'enable.idempotence': True,
    'transactional.id': 'my-transactional-id'
}

producer = Producer(producer_config)
producer.init_transactions()

# Begin transaction
# Produce three messages to 'eos_topic'
# Commit transaction
# Your code here

Hint

Use begin_transaction() before producing messages and commit_transaction() after.

4

Print confirmation after commit

Add a print statement that outputs exactly "Transaction committed successfully!" after the transaction commit.

Kafka

from confluent_kafka import Producer

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'enable.idempotence': True,
    'transactional.id': 'my-transactional-id'
}

producer = Producer(producer_config)
producer.init_transactions()

producer.begin_transaction()
producer.produce('eos_topic', key='key1', value='message1')
producer.produce('eos_topic', key='key2', value='message2')
producer.produce('eos_topic', key='key3', value='message3')
producer.commit_transaction()

# Print confirmation message
# Your code here

Hint

Use print("Transaction committed successfully!") exactly.

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