Exactly-once stream processing in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does exactly-once stream processing mean in Kafka?

It means each message is processed only one time, no duplicates or missed messages, even if failures happen.

intermediate

What Kafka feature helps achieve exactly-once processing?

Kafka uses transactions to group writes and commits atomically, ensuring messages are processed exactly once.

beginner

Why is idempotence important for exactly-once processing?

Idempotence means repeating an action has the same effect as doing it once, preventing duplicates in failures.

intermediate

How does Kafka Streams API support exactly-once semantics?

Kafka Streams uses transactions and state stores to commit results atomically, avoiding duplicates on restarts.

beginner

What is the role of producer idempotence in Kafka exactly-once processing?

Producer idempotence ensures that resending the same message does not create duplicates in Kafka topics.

Which Kafka feature is essential for exactly-once processing?

A Transactions

B Consumer groups

C Partitions

D Replication

Transactions allow grouping of writes and commits atomically, enabling exactly-once processing.

What does idempotence prevent in Kafka producers?

A Slow consumers

B Message loss

C Duplicate messages

D Partition rebalancing

Idempotence prevents duplicate messages when producers retry sending.

Exactly-once processing guarantees that messages are:

A Processed twice

B Processed at most once

C Processed at least once

D Processed exactly once

Exactly-once means each message is processed one and only one time.

Kafka Streams achieves exactly-once semantics by:

A Using only consumer groups

B Using transactions and state stores

C Disabling replication

D Using manual offset commits

Transactions and state stores allow atomic commits and fault tolerance.

What happens if a Kafka producer is not idempotent and retries sending a message?

A Duplicate messages may appear

B Partition rebalances

C Consumer crashes

D Message is lost

Without idempotence, retries can cause duplicate messages.

Explain how Kafka achieves exactly-once stream processing.

Think about how Kafka groups writes and commits to avoid duplicates.

Why is idempotence important for Kafka producers in exactly-once processing?

Consider what happens when a message is sent multiple times due to failure.

Practice

1. What is the main benefit of exactly-once stream processing in Kafka?

easy

A. It ensures messages are processed only once, avoiding duplicates.

B. It speeds up message delivery by skipping acknowledgments.

C. It allows messages to be processed multiple times for safety.

D. It disables message ordering to improve throughput.

Solution

1. Step 1: Understand exactly-once processing goal

   Exactly-once processing means each message affects the system only once, preventing duplicates.

2. Step 2: Compare options with this goal

   Only It ensures messages are processed only once, avoiding duplicates. describes avoiding duplicates by processing messages once.

3. Final Answer:

   It ensures messages are processed only once, avoiding duplicates. -> Option A

4. Quick Check:

   Exactly-once = no duplicates [OK]

Hint: Exactly-once means no duplicate effects on data [OK]

Common Mistakes:

• Confusing exactly-once with at-least-once processing
• Thinking it speeds up delivery by skipping steps
• Assuming it allows multiple processing for safety

2. Which Kafka producer configuration enables exactly-once semantics?

easy

A. compression.type = none

B. enable.idempotence = true

C. acks = 0

D. max.in.flight.requests.per.connection = 10

Solution

1. Step 1: Identify config for exactly-once

   Enabling idempotence ensures the producer can retry without duplicates.

2. Step 2: Match config options

   Only 'enable.idempotence = true' enables this feature.

3. Final Answer:

   enable.idempotence = true -> Option B

4. Quick Check:

   Idempotence enabled = exactly-once [OK]

Hint: Idempotence true enables exactly-once in Kafka producer [OK]

Common Mistakes:

• Choosing acks=0 which disables acknowledgments
• Confusing compression with processing guarantees
• Setting max.in.flight.requests without idempotence

3. Given this Kafka Streams code snippet, what is the output if a failure occurs before commit?

streams.start();
try {
  streams.process(record);
  streams.commitTransaction();
} catch (Exception e) {
  streams.abortTransaction();
}

medium

A. Processed record is committed multiple times.

B. Processed record may be duplicated after restart.

C. Processed record is committed exactly once.

D. Processed record is lost and not committed.

Solution

1. Step 1: Analyze transaction handling

   If an exception occurs before commit, abortTransaction() is called, rolling back changes.

2. Step 2: Determine output effect

   Rollback means the processed record is not committed and effectively lost in this run.

3. Final Answer:

   Processed record is lost and not committed. -> Option D

4. Quick Check:

   Abort transaction = no commit = lost record [OK]

Hint: Abort transaction means no commit, so data is lost [OK]

Common Mistakes:

• Assuming record is committed despite failure
• Thinking abortTransaction duplicates records
• Confusing commitTransaction with abortTransaction

4. Identify the error in this Kafka Streams code snippet for exactly-once processing:

props.put("enable.idempotence", "true");
props.put("transactional.id", "txn-1");
KafkaProducer producer = new KafkaProducer(props);
producer.beginTransaction();
producer.send(record);
// Missing commit or abort here
producer.close();

medium

A. Missing commitTransaction or abortTransaction before close.

B. enable.idempotence should be false for transactions.

C. transactional.id must be unique per message.

D. KafkaProducer cannot be closed after sending messages.

Solution

1. Step 1: Review transaction lifecycle

   After beginTransaction and send, a commit or abort must finalize the transaction.

2. Step 2: Identify missing step

   The code closes producer without committing or aborting, causing incomplete transaction.

3. Final Answer:

   Missing commitTransaction or abortTransaction before close. -> Option A

4. Quick Check:

   Transactions need commit or abort before close [OK]

Hint: Always commit or abort before closing producer [OK]

Common Mistakes:

• Thinking idempotence false is needed for transactions
• Believing transactional.id changes per message
• Assuming producer close auto-commits transactions

5. You want to build a Kafka Streams application that updates user balances exactly once, even if failures occur. Which approach ensures this behavior?

hard

A. Process messages without committing offsets to avoid duplicates.

B. Disable transactions and rely on at-least-once processing with retries.

C. Use idempotent producer with transactions and commit offsets atomically.

D. Use multiple producers without transactions to increase throughput.

Solution

1. Step 1: Understand exactly-once requirements

   Exactly-once needs atomic commit of data and offsets to avoid duplicates or loss.

2. Step 2: Match approach to requirements

   Using idempotent producer with transactions and atomic offset commits ensures exactly-once updates.

3. Final Answer:

   Use idempotent producer with transactions and commit offsets atomically. -> Option C

4. Quick Check:

   Idempotent + transactions + atomic commit = exactly-once [OK]

Hint: Atomic commit with idempotent producer ensures exactly-once [OK]

Common Mistakes:

• Relying on retries without transactions causes duplicates
• Using multiple producers without coordination breaks exactly-once
• Not committing offsets leads to message reprocessing