[
https://issues.apache.org/jira/browse/KAFKA-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-17898.
------------------------------------
Resolution: Fixed
> Seperate Epoch Bump Scenarios and Error Handling in TV2
> -------------------------------------------------------
>
> Key: KAFKA-17898
> URL: https://issues.apache.org/jira/browse/KAFKA-17898
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Ritika Reddy
> Assignee: Ritika Reddy
> Priority: Major
>
> With KAFKA-14562, we implemented epoch bump on both the client and the
> server. Mentioned below are the different epoch bump scenarios we have on
> hand after enabled tv2
> h3. Non-Transactional Producers
> * Epoch bumping is always allowed.
> * Different code paths used to handle epoch bumping.
> h3. Transactional Producers
> * _No Epoch Bump Allowed_
> ** coordinatorSupportsBumpingEpoch = false when initPIDVersion <3 or null
> * _Client Triggered Epoch Bump Allowed_
> ** coordinatorSupportsBumpingEpoch = true when initPIDVersion >= 3
> ** TransactionVersion2Enabled = false when endTxnVersion < 5
> * _Only Server Triggered Epoch Bump Allowed_
> ** Transaction Version 2 = true and endTxnVersion >= 5
>
> We want to refine the code and make it more structured to correctly handle
> epoch bumping in the above mentioned cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
