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

Flink Jira Bot updated FLINK-29128:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> Uncatch IllegalStateException found when log split changes handling result in 
> KafkaPartitionSplitReader
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-29128
>                 URL: https://issues.apache.org/jira/browse/FLINK-29128
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.14.5, 1.15.3
>            Reporter: Leo zhang
>            Assignee: Leo zhang
>            Priority: Minor
>              Labels: pull-request-available, stale-assigned
>
> When logger is set to debug mode, 
> KafkaPartitionSplitReader#maybeLogSplitChangesHandingResult log the handing 
> result of allĀ  SplitsChange<KafkaPartitionSplit>, and the handling result 
> include the kafka partition's starting offset, which is get from kafka 
> api(consumer.position).
> When a SplitsChange<KafkaPartitionSplit> is a empty split,it will be 
> removed(unassign partition), IllegalStateException will be thrown by 
> consumer.position, since we can only check the position for partitions 
> assigned to the consumer.And this exception has not been catch, and is 
> rethrown as RuntimeExption, which lead to a failure of the application's 
> execution.



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

Reply via email to