Status

Current state: Under Voting  Complete 

Discussion thread: here

JIRA: here 

...

• Retry the operation without bothering the application (retriable)

• Share with the application that an error has occurred, but the client can recover if the transaction is aborted by the client and under the covers, the epoch is bumped (abortable)

• Share with the application that an error has occurred, and there is no way to recover except shut down the client (fatal)

...

We are proposing to group exceptions into four types:

1. Producer-Retriable: mostly maps onto current retriable errors. The producer can handle the retry on its own and the failure is invisible to the application. Some of these errors may indicate that a metadata update at the producer level is required. Because of that we introduce a few two subclasses to the retriable error

   1. retry only (just send the request again – after some period of backoff)

   2. refresh metadata and retry (request metadata and maybe modify the request before resending)

2. Producer-Abortable: mostly maps onto abortable errors. The error is bubbled to the application layer, and it can choose to roll back any state from the ongoing transaction and abort the transaction. The producer does not need to restart, as after aborting, it can be confident that the state was as it was before the transaction started. The application can also close the producer and react as it does for application-recoverable cases, but it doesn’t need to.

3. Application-Recoverable: maps on to some fatal errors. The error is bubbled to the application layer, and it may need to do a bit more to roll back and clean up state. The producer can not simply abort and know the current state of the partitions. Applications can handle this in different ways – streams Kafka Streams may rebalance a task and/or close the task and restart it. Another application may read from their own checkpoint to continue. In any case, the producer must restart and will be unusable after encountering this error.

4. Invalid-Configuration: maps to some fatal errors. The error is bubbled up to the application layer. The application can decide what to do. The producer doesn’t need to restart, but the application may chose to close it.

Each error code always represent the same class and rarely rely on client state to determine how to handle. While  Additionally, while it is good to have a mapping, It is also useful to have a general strategy – ie a typical unknown error (not specified by the client to have a type) should probably be application recoverable.

Exception Table 

Note: For Retriable errors, the producer handles retries internally, keeping the failure details hidden from the application. Conversely, other types of exceptions will be surfaced to the application code for handling.

Exception Table 

Below table contains list of exceptions with current Below table contains list of exceptions with current and New handing. All exceptions are grouped under a header which represent Exception Name:

Yellow → Needs modificationGreen Image Removed → New exceptions added as part of this KIP

Check → Exception handling match as mentioned in KIP-691

Cross → Exception handling doesn't match as mentioned in KIP-691

...

RetriableException

ProducerRetriableTransactionException

ProducerRefreshRetriableTransactionException

RefreshRetriableException

...

TransactionAbortableException

ApplicationRecoverableException

IllegalStateException

Abortable

Exception/Error Names	Current handling		New Handling
	Producer API	Transaction API	Producer API	Transaction API	Comments
IllegalStateException	Abortable

Sometimes Fatal depending on whether application or Sender caused issue. See: kafka: KAFKA-14831: Illegal state errors should be fatal in transactional producerCLOSED

Application Recoverable (probably not expected) Image Modified

Application RecoverableImage Modified

InvalidProducerEpochException

Abortable

Fatal

Application Recoverable Image Removed

Application Recoverable Image Removed

ProducerFencedException

Fatal

Fatal

Application Recoverable Image Removed

Application Recoverable Image Removed

InvalidPidMappingException

Sometimes retriable (no longer returned) or abortable

Abortable

Application Recoverable Image Removed

Application Recoverable Image Removed

We will handle all default exceptions as generic unknown errors, which will be application recoverable
	KafkaException	Abortable (default seems to be abortable)	Fatal in most cases, but abortable when there are partition errors	Application Recoverable (not expected) Image Added	Application Recoverable (not expected) Image Added
	RuntimeException	Abortable (default seems to be abortable)	Fatal – only thrown as this generic type when correlation ID is wrong. This should be updated as KIP-691 suggests	Application Recoverable (not expected) Image Added	Application Recoverable (not expected) Image Added
InvalidProducerEpochException	Abortable	Fatal

UnknownProducerIdException

Sometimes retriable (no longer returned) or abortable

Abortable

Application Recoverable Image Modified

Application Recoverable

Image Removed

Image Added

FencedInstanceIdException

ProducerFencedException	Fatal	Fatal	Application Recoverable Image Added	Application Recoverable Image Added
InvalidPidMappingException	Sometimes retriable (no longer returned) or abortable	Abortable	Application Recoverable Image Added	Application Recoverable Image Added
FencedInstanceIdException CommitFailedException UnknownMemberIdException IllegalGenerationExceiption	N/A	Abortable (TxnOffsetCommit Only)	N/A	Application Recoverable Image Modified

KafkaException

Abortable (default seems to be abortable)

Fatal in most cases, but abortable when there are partition errors

Application Recoverable (not expected) Image Removed

Application Recoverable (not expected) Image Removed

RuntimeException

Abortable (default seems to be abortable)

Fatal – only thrown as this generic type when correlation ID is wrong. This should be updated as KIP-691 suggests

Application Recoverable (not expected) Image Removed

Application Recoverable (not expected) Image Removed

CorrelationIdMismatchException

Application Recoverable

Application Recoverable

InvalidConfigurationTransactionException

InvalidConfigurationException

InvalidTxnStateException requires special handling where producer API and Transactional API has different handling:

...

...

Current handling

...

Expected Handling

...

Producer API

...

Transaction API

...

Producer API

...

Transaction API

...

InvalidTxnStateException

...

Abortable

...

Fatal

...

...

Public Interfaces

We have below exception classes available in current Kafka code

// Producer Abortable Transaction
public class TransactionAbortableException extends ApiException {
    ...
}

//Producer Retriable  
public abstract class RetriableException

Public Interfaces

We will add new exception types, as listed in the table below, that extend the existing exceptions.

// Producer Abortable Transaction
public class AbortableTransactionException extends ApiException {
     ...
}


//Producer Retriable Invalid-Configuration
public class ProducerRetriableTransactionExceptionInvalidConfigurationException extends ApiException {
 	...
}

We will add new exception types, as listed in the table below, that extend the existing exceptions.

//Producer Refresh and Retriable
public abstract class ProducerRefreshRetriableTransactionExceptionRefreshRetriableException extends ApiExceptionRetriableException {
	...
}

//Application-Recoverable new
public abstract class ApplicationRecoverableTransactionExceptionApplicationRecoverableException extends ApiException {
    ...
}

// Invalid-Configuration

We will extend below existing exceptions types to maintain class hierarchy 

// UnknownTopicOrPartitionException and NotLeaderOrFollowerException  extends InvalidMetadataException 
public class InvalidConfigurationTransactionExceptionInvalidMetadataException extends ApiExceptionRefreshRetriableException {
 	...
}

Client side code example

// TopicAuthorizationException and GroupAuthorizationException extends AuthorizationException 
public class AuthorizationException extends InvalidConfigurationException {
	...
}

Client side code example

public class TransactionalClientDemo {

    private static 

public class TransactionalClientDemo {

    private static final String CONSUMER_GROUP_ID = "my-group-id";
    private static final String OUTPUT_TOPIC = "output";
    private static final String INPUT_TOPIC = "input";
    private static KafkaConsumer<String, String> consumer;
    private static KafkaProducer<String, String> producer;

    public static void main(String[] args) {
        initializeApplication();

        boolean isRunning = true;
        // Continuously poll for records
        while (isRunning) {
            try {
                try {
                    // Poll records from Kafka for a timeout of 60 seconds
                    ConsumerRecords<String, String> records = consumer.poll(ofSeconds(60));

                    // Process records to generate word count map
                    Map<String, Integer> wordCountMap = new HashMap<>();

                    for (ConsumerRecord<String, String> record : records) {
                        String[] words = record.value().split(" ");
                        for (String word : words) {
						  wordCountMap.merge(word, 1, Integer::sum);
                        wordCountMap.merge(word, 1, Integer::sum);
}
                        }
                    }

                    // Begin transaction
                    producer.beginTransaction();

                    // Produce word count results to output topic
                    wordCountMap.forEach((key, value) ->
                            producer.send(new ProducerRecord<>(OUTPUT_TOPIC, key, value.toString())));

                    // Determine offsets to commit
                    Map<TopicPartition, OffsetAndMetadata> offsetsToCommit = new HashMap<>();
                    for (TopicPartition partition : records.partitions()) {
                        List<ConsumerRecord<String, String>> partitionedRecords = records.records(partition);
                        long offset = partitionedRecords.get(partitionedRecords.size() - 1).offset();
                        offsetsToCommit.put(partition, new OffsetAndMetadata(offset + 1));
                    }

                    // Send offsets to transaction for atomic commit
                    producer.sendOffsetsToTransaction(offsetsToCommit, CONSUMER_GROUP_ID);

                    // Commit transaction
                    producer.commitTransaction();
                } catch (AbortableTransactionExceptionTransactionAbortableException e) {
                    // Abortable Exception: Handle Kafka exception by aborting transaction. producer.abortTransaction() should not throw abortable exception.
                    producer.abortTransaction();
                    resetToLastCommittedPositions(consumer);
                }
            } catch (InvalidConfigurationTransactionExceptionInvalidConfigurationException e) {
                //  Fatal Error: The error is bubbled up to the application layer. The application can decide what to do
                closeAll();
                throw e;
            } catch (KafkaException | ApplicationRecoverableTransactionExceptionApplicationRecoverableException e) {
                // Application Recoverable: The application must restart
                closeAll();
                initializeApplication();
            }
        }

    }

Full example can be accessed at: https://github.com/apache/kafka/pull/15913/files 

Compatibility, Deprecation, and Migration Plan

Note: The producer.abortTransaction() method will not throw an abortable exception to avoid creating a loop.

Compatibility, Deprecation, and Migration Plan

For applications using older code

For existing errors, if the application code already handles the error, it will continue to do so. However, the new TransactionAbortableException  introduced in KIP-890 extends KafkaException, which is treated as fatal by applications. Therefore, we expect TransactionAbortableException  to also be treated as fatal by older code.

Currently, the transactional producer.send returns retriable exception types, such as TimeoutException , which poses a risk of duplicates in Kafka. In this KIP, we will update the transactional producer.send path such that all retriable exceptions will be translated to TransactionAbortableException. Older clients that are using the transactional producer and handling TimeoutException  by retrying the produce operation can update to handle TransactionAbortableException .

For applications using newer code

Applications using newer code, as mentioned in Clientsidecodeexample, have the flexibility to adjust their exception handling logic based on the specific type of exception encountered, enabling them to take appropriate actions.

Handling for OutOfOrderSequenceException  requires additional considerations which is out of scope for this KIP.  OutOfOrderSequenceException  and UnknownProducerIdException  (which extends OutOfOrderSequenceException  ) will not be categorised under any of the defined exception groups in this KIP. This will not impact applications using newer codeThis KIP involves client side changes which only affects the resiliency of new Producer client and Streams. New clients have the flexibility to adjust their exception handling logic based on the specific type of exception encountered, enabling them to take appropriate actions as described in the Clientsidecodeexample section. Existing clients need not make any modifications, as they can continue to utilize their current error handling mechanisms.

Test Plan

We will add additional integration and unit tests to check if client acts as expected.

...