[jira] [Updated] (FLINK-39072) Handle InvalidPidMappingException as known failure in KafkaCommitter

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-39072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-39072:
-----------------------------------
    Labels: pull-request-available  (was: )

> Handle InvalidPidMappingException as known failure in KafkaCommitter
> --------------------------------------------------------------------
>
>                 Key: FLINK-39072
>                 URL: https://issues.apache.org/jira/browse/FLINK-39072
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Natea Eshetu Beshada
>            Assignee: Natea Eshetu Beshada
>            Priority: Major
>              Labels: pull-request-available
>
> When a Kafka transaction's producer ID mapping expires on the broker, commitTransaction() throws InvalidPidMappingException. Previously this fell through to the generic Exception handler, calling signalFailedWithUnknownReason which triggers a failover. On recovery the same expired transaction is replayed, causing an infinite restart loop.
> Catch InvalidPidMappingException explicitly and call signalFailedWithKnownReason so the framework's configured strategy can handle it (e.g., skip the unrecoverable transaction).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)