You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Arvid Heise (Jira)" <ji...@apache.org> on 2026/06/29 12:48:00 UTC
[jira] [Commented] (FLINK-39728) KafkaPartitionSplitReader.pauseOrResumeSplits throws IllegalStateException on concurrently unassigned partitions
[ https://issues.apache.org/jira/browse/FLINK-39728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092306#comment-18092306 ]
Arvid Heise commented on FLINK-39728:
-------------------------------------
Merged as eb8ff700b2390d5bc3a8c67fcdb3f3ad93824e24.
> KafkaPartitionSplitReader.pauseOrResumeSplits throws IllegalStateException on concurrently unassigned partitions
> ----------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-39728
> URL: https://issues.apache.org/jira/browse/FLINK-39728
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Reporter: Jim Hughes
> Assignee: Jim Hughes
> Priority: Major
> Labels: pull-request-available
>
> KafkaPartitionSplitReader.pauseOrResumeSplits throws IllegalStateException on concurrently unassigned partitions
> KafkaPartitionSplitReader.pauseOrResumeSplits() calls consumer.pause() and consumer.resume() with the full set of requested partitions without checking whether those partitions are still part of the consumer's current assignment.
> Between the time the source reader decides which splits to pause/resume and the time pauseOrResumeSplits() executes, a partition can be unassigned by a concurrent fetch() call (which removes finished splits) or by removeEmptySplits(). When this happens, the Kafka consumer throws:
> {code}
> java.lang.IllegalStateException: No current assignment for partition <topic>-<partition>
> {code}
> This crashes the source reader even though the correct behavior is to silently skip partitions that are no longer assigned — pausing or resuming an unassigned partition is a no-op by definition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)