[ 
https://issues.apache.org/jira/browse/FLINK-31006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804363#comment-17804363
 ] 

Jonas Weile edited comment on FLINK-31006 at 1/8/24 4:31 PM:
-------------------------------------------------------------

Hi!

Is this issue is still being worked on? I am still able to reproduce it and 
would like to work on a solution.

I have created a suggestion as a [github pull 
request|[https://github.com/apache/flink-connector-kafka/pull/71]] but would 
very much like to open up a new round of discussions?


was (Author: JIRAUSER302117):
Hi!

Is this issue is still being worked on? I am still able to reproduce it and 
would like to work on a solution.

I have created a suggestion as a [github pull 
request|[https://github.com/apache/flink-connector-kafka/pull/71],] but would 
very much like to open up a new round of discussions?

> job is not finished when using pipeline mode to run bounded source like 
> kafka/pulsar
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-31006
>                 URL: https://issues.apache.org/jira/browse/FLINK-31006
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka, Connectors / Pulsar
>    Affects Versions: 1.17.0
>            Reporter: Jacky Lau
>            Assignee: Jacky Lau
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>             Fix For: 1.19.0
>
>         Attachments: image-2023-02-10-13-20-52-890.png, 
> image-2023-02-10-13-23-38-430.png, image-2023-02-10-13-24-46-929.png, 
> image-2023-03-04-01-04-18-658.png, image-2023-03-04-01-05-25-335.png, 
> image-2023-03-04-01-07-04-927.png, image-2023-03-04-01-07-36-168.png, 
> image-2023-03-04-01-08-29-042.png, image-2023-03-04-01-09-24-199.png
>
>
> when i do failover works like kill jm/tm when using  pipeline mode to run 
> bounded source like kafka, i found job is not finished, when every partition 
> data has consumed.
>  
> After dig into code, i found this logical not run when JM recover. the 
> partition infos are not changed. so noMoreNewPartitionSplits is not set to 
> true. then this will not run 
>  
> !image-2023-02-10-13-23-38-430.png!
>  
> !image-2023-02-10-13-24-46-929.png!



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

Reply via email to