...

• DuplicateSequenceNumber [NEW]

• InvalidSequenceNumber [NEW]

• ProducerFenced InvalidProducerEpoch [NEW]

• UNSUPPORTED_FOR_MESSAGE_FORMAT

...

AddPartitionsToTxnResponse => ErrorCode
 ErrorCode: int16

Error code:

• Ok

• ProducerFencedInvalidProducerEpoch

• InvalidPidMapping

• NotCoordinatorForTransactionalId

• CoordinatorNotAvailable

• InvalidTxnRequest

...

AddOffsetsToTxnResponse => ErrorCode
 ErrorCode: int16
 Coordinator => NodeId Host Port
   NodeId => int32
   Host => string
   Port => int32

Error code:

• Ok

• ProducerFencedInvalidProducerEpoch

• InvalidPidMapping

• NotCoordinatorForTransactionalId

• CoordinatorNotAvailable

• InvalidTxnRequest

...

EndTxnResponse => ErrorCode
 ErrorCode => int16

Error code:

• Ok

• ProducerFencedInvalidProducerEpoch

• InvalidPidMapping

• CoordinatorNotAvailable

• NotCoordinatorForTransactionalId

• InvalidTxnRequest

...

TxnOffsetCommitResponse => [TopicName [Partition ErrorCode]]]
 TopicName => string
 Partition => int32
 ErrorCode => int16

Error code:

• ProducerFencedInvalidProducerEpoch

Message Format

In order to add new fields such as PID and epoch into the produced messages for transactional messaging and de-duplication, we need to change Kafka’s message format and bump up its version (i.e. the “magic byte”). More specifically, we need to add the following fields into each message:

...