You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Anish Shrigondekar (Jira)" <ji...@apache.org> on 2025/09/16 22:08:00 UTC

[jira] [Closed] (SPARK-53560) Crash looping when retrying uncommitted batch in Kafka source and AvailableNow trigger

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

Anish Shrigondekar closed SPARK-53560.
--------------------------------------

> Crash looping when retrying uncommitted batch in Kafka source and AvailableNow trigger
> --------------------------------------------------------------------------------------
>
>                 Key: SPARK-53560
>                 URL: https://issues.apache.org/jira/browse/SPARK-53560
>             Project: Spark
>          Issue Type: Bug
>          Components: Structured Streaming
>    Affects Versions: 3.4.0, 4.1.0
>            Reporter: Yuchen Liu
>            Assignee: Yuchen Liu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.1.0, 3.5.7, 4.0.2
>
>
> There is a crash loop when using Kafka source with AvailableNow. It will be triggered deterministically when the query fails / terminates in the middle of the run, and the user changes the Kafka topic partition, then restarts the query. This is because the topic partitions in uncommitted batch and the latest topic partitions aren't the same, but trigger.AvailableNow requires it anyway.
> This PR solves the issue by not fetching the latest topic partitions in function `prepareForTriggerAvailableNow`. Instead, it fetches in `latestOffset`, because Spark will not call `latestOffset` when retrying the uncommitted batch.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org