Kaushik Raina 8c71ab03b5 KAFKA-19176: Update Transactional producer to translate retriable into abortable exceptions (#19522) ... ### Problem - Currently, when a transactional producer encounters retriable errors (like `COORDINATOR_LOAD_IN_PROGRESS`) and exhausts all retries, finally returns retriable error to Application Layer. - Application reties can cause duplicate records. As a fix we are transitioning all retriable errors as Abortable Error in transaction producer path. - Additionally added InvalidTxnStateException as part of https://issues.apache.org/jira/browse/KAFKA-19177 ### Solution - Modified the TransactionManager to automatically transition retriable errors to abortable errors after all retries are exhausted. This ensures that applications can abort transaction when they encounter `TransactionAbortableException` - `RefreshRetriableException` like `CoordinatorNotAvailableException` will be refreshed internally [[code](6c26595ce3/clients/src/main/java/org/apache/kafka/clients/producer/internals/TransactionManager.java (L1702-L1705))] till reties are expired, then it will be treated as retriable errors and translated to `TransactionAbortableException` - Similarly for InvalidTxnStateException ### Testing Added test `testSenderShouldTransitionToAbortableAfterRetriesExhausted` to verify in sender thread: - Retriable errors are properly converted to abortable state after retries - Transaction state transitions correctly and subsequent operations fail appropriately with TransactionAbortableException Reviewers: Justine Olshan <jolshan@confluent.io>		2025-06-03 10:21:22 -07:00
..
clients-integration-tests/src/test	KAFKA-19349 Move CreateTopicsRequestWithPolicyTest to clients-integration-tests (#19849)	2025-06-03 02:52:07 +08:00
src	KAFKA-19176: Update Transactional producer to translate retriable into abortable exceptions (#19522)	2025-06-03 10:21:22 -07:00
.gitignore	KAFKA-4848: Fix retryWithBackoff deadlock issue	2017-03-20 21:56:15 -07:00