You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ritika Reddy (Jira)" <ji...@apache.org> on 2025/05/12 22:11:00 UTC
[jira] [Updated] (KAFKA-19272) Handling different scenarios for initPid(keepPrepared=true)
[ https://issues.apache.org/jira/browse/KAFKA-19272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ritika Reddy updated KAFKA-19272:
---------------------------------
Description:
When initPid(keepPrepared = true) is called when a client crashes, there are quite a few situations that we should consider.
When there is an ongoing txn, we can transition it to the newly added PREPARED_TRANSACTION state, but what if there's no ongoing transaction?
Another scenario could be:
# Issued a commit, to commit prepared
# The commit succeeded on the TC, but the client crashed
# Client restarted with keepPreparedTxn=true (because it doesn't know if the commit succeeded or not and needs to keep retrying the commit until it's successful)
# Issued a commit, but the transaction is not ongoing, because it's committed
was:
When initPid(keepPrepared = true) is called when a client crashes, there are quite a few situations that we should consider.
When there is an ongoing txn we can transition it to the newly added PREPARED_TRANSACTION state but what if there's no ongoing transaction?
> Handling different scenarios for initPid(keepPrepared=true)
> -----------------------------------------------------------
>
> Key: KAFKA-19272
> URL: https://issues.apache.org/jira/browse/KAFKA-19272
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Ritika Reddy
> Assignee: Ritika Reddy
> Priority: Major
>
> When initPid(keepPrepared = true) is called when a client crashes, there are quite a few situations that we should consider.
> When there is an ongoing txn, we can transition it to the newly added PREPARED_TRANSACTION state, but what if there's no ongoing transaction?
> Another scenario could be:
> # Issued a commit, to commit prepared
> # The commit succeeded on the TC, but the client crashed
> # Client restarted with keepPreparedTxn=true (because it doesn't know if the commit succeeded or not and needs to keep retrying the commit until it's successful)
> # Issued a commit, but the transaction is not ongoing, because it's committed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)