jolshan commented on code in PR #17698: URL: https://github.com/apache/kafka/pull/17698#discussion_r1859417510
########## core/src/main/scala/kafka/coordinator/transaction/TransactionCoordinator.scala: ########## @@ -564,41 +627,44 @@ class TransactionCoordinator(txnConfig: TransactionConfig, else PrepareAbort - // Maybe allocate new producer ID if we are bumping epoch and epoch is exhausted - val nextProducerIdOrErrors = - if (clientTransactionVersion.supportsEpochBump() && !txnMetadata.pendingState.contains(PrepareEpochFence) && txnMetadata.isProducerEpochExhausted) { - try { - Right(producerIdManager.generateProducerId()) - } catch { - case e: Exception => Left(Errors.forException(e)) - } + generateTxnTransitMetadataForTxnCompletion(nextState, false) + case CompleteCommit => + if (currentTxnMetadataIsAtLeastTransactionsV2) { + if (txnMarkerResult == TransactionResult.COMMIT) { + if (isRetry) + Left(Errors.NONE) + else + logInvalidStateTransitionAndReturnError(transactionalId, txnMetadata.state, txnMarkerResult) } else { - Right(RecordBatch.NO_PRODUCER_ID) + if (isRetry) + logInvalidStateTransitionAndReturnError(transactionalId, txnMetadata.state, txnMarkerResult) + else + generateTxnTransitMetadataForTxnCompletion(PrepareAbort, true) Review Comment: for this case, shouldn't we be checking clientTransactionVersion.supportsEpochBump()? For all the empty/complete transitions, it doesn't matter if the current metadata was v2 but if the new transaction is using v2 right? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org