Thanks folks. This is really helpful.
Regards.
Meghajit
On Sun, Jun 19, 2022 at 1:24 AM Jing Ge wrote:
> Hi Meghajit,
>
> Thanks for the feedback. I have fired a ticket:
> https://issues.apache.org/jira/browse/FLINK-28117
>
> Best regards,
> Jing
>
> On Mon, Jun 13, 2022 at 7:23 AM Meghajit Maz
The document also suggest not cancelling a job with savepoint. Can you try to
execute “flink stop -s [savepoint dir] ” and then execute “flink cancel
”? You can send us the execution logs for above two commands.
> On 19 Jun 2022, at 10:13 PM, Sudharsan R wrote:
>
> Hi Yu'an,
> We use flink
Hi Yu'an,
We use flink 1.11.1. This version has a 'cancel' option in the CLI (
https://nightlies.apache.org/flink/flink-docs-release-1.11/ops/cli.html)
So, we do flink cancel -s . We have had
innumerable 'job cancels' during deployments and we have never seen
anything like the sequence above. So,
Hi Sudharsan,
How did you cancel thus single job. According to the High Availability
Document:
“In order to recover submitted jobs, Flink persists metadata and the job
artifacts. The HA data will be kept until the respective job either succeeds,
is cancelled or fails terminally. Once this ha
退订请发送任意消息至user-unsubscr...@flink.apache.org
In order to unsubscribe, please send an email to
user-unsubscr...@flink.apache.org
Thanks
Best regards,
Jing
From: liangzai
Date: Sun, Jun 19, 2022 at 4:37 AM
Subject: Re: New KafkaSource API: Change in default behavior regarding
starting offset
To:
