Introducing Exactly Once Semantics To Apache Kafka

1
Introducing Exactly Once
Semantics in Apache Kafka
Jason Gustafson, Guozhang Wang, Sriram
Subramaniam, and Apurva Mehta

2
On deck..
• Kafka’s existing delivery semantics.
• Why did we improve them?
• What’s new?
• How do you use it?
• Summary.

3
Apache Kafka’s existing semantics

13
TL;DR – What we have today
• At least once in order delivery per partition.
• Producer retries can introduce duplicates.

15
Why improve?
• Stream processing is becoming an ever bigger part of the
data landscape.
• Apache Kafka is the heart of the streams platform.
• Strengthening Kafka’s semantics expands the universe of
streaming applications.

16
A motivating example..
A peer to peer lending platform which processes micro-loans
between users.

23
What’s new
• Exactly once in order delivery per partition
• Atomic writes across multiple partitions
• Performance considerations

24
What’s new, Part 1
Exactly once, in order, delivery per partition

33
TL;DR
• Sequence numbers and producer ids:
• enable de-dup
• are in the log.
• Hence de-dup works transparently across leader
changes.
• Will not de-dup application-level resends.
• Works transparently – no API changes.

34
What’s new, part 2
Multi partition writes.

35
Introducing ‘transactions’
producer.initTransactions();
try {
producer.beginTransaction();
producer.send(record0);
producer.sendOffsetsToTxn(…);
producer.commitTransaction();
} catch (ProducerFencedException e) {
producer.close();
} catch (KafkaException e) {
producer.abortTransaction();
}

36
Introducing ‘transactions’

37
Initializing ‘transactions’

38
Transactional sends – part 1

39
Transactional sends – part 2

44
Let’s review the APIs
try {
producer.close();
}

45
try {
producer.close();
}

46
try {
producer.close();
}

47
try {
producer.close();
}

48
try {
producer.close();
}

49
Consumer returns only committed messages

50
Some notes on consuming transactions
• Two ‘isolation levels’ : read_committed, and
read_uncommitted.
• Messages read in offset order.
• read_committed consumers read to the point where there
are no open transactions.

51
TL;DR
• Transaction coordinator and transaction log maintain
transaction state.
• Use the new producer APIs for transactions.
• Consumers can read only committed messages.

53
What’s new, part 3: Performance boost!
• Up to +20% producer throughput
• Up to +50% consumer throughput
• Up to -20% disk utilization
• Savings start when you batch
• Details: https://bit.ly/kafka-eos-perf

54
Too good to be true?
Let’s understand how!

57
The new format -> new fields

58
The new format -> new fields

59
The new format -> delta encoding

60
A visual comparison with 7 records, 10 bytes each

61
TL;DR
• With a batch size of 2, the new format starts saving
space.
• Savings are maximal for large batches of small
messages.
• Hence higher throughput when IO bound.
• Works as soon as you upgrade to the new format.

62
Cool!
But how do I use this?

63
Producer Configs
• enable.idempotence = true
• max.inflight.requests.per.connection=1
• acks = “all”
• retries > 1 (preferably MAX_INT)
• transactional.id = ‘some unique id’
• enable.idempotence = true

64
Consumer configs
• isolation.level:
• “read_committed”, or
• “read_uncommitted”

65
Streams config
• processing.mode = “exactly_once”

66
Putting it together
• We understood Kafka’s existing delivery semantics
• Understood why we want to improve them
• Learned how these have been strengthened
• Learned how the new semantics work

67
When is it available?
Available to try in Kafka 0.11, June 2017.

Introducing Exactly Once Semantics To Apache Kafka

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to Introducing Exactly Once Semantics To Apache Kafka (20)

Recently uploaded (20)

Introducing Exactly Once Semantics To Apache Kafka

Editor's Notes