Thanks Zhanghao && Hang. I am familiar with the flink savepoint feature. The exact offset position is stored in savepoint and the job can be resumed from the savepoint using the offset position that is stored in it. But I am not sure whether the exact offset position is committed to kafka when doing savepoint. If the answer is yes, i can ensure no repeat consumption even the state is incompatible because i can stop with savepoint and submit the job without savepoint Thanks, Lei
On Thu, Jun 6, 2024 at 10:50 AM Zhanghao Chen <zhanghao.c...@outlook.com> wrote: > Hi, you could stop the job with a final savepoint [1]. Flink which will > trigger a final offset commit on the final savepoint. > > [1] > https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/cli/#stopping-a-job-gracefully-creating-a-final-savepoint > > Best, > Zhanghao Chen > ------------------------------ > *From:* Lei Wang <leiwang...@gmail.com> > *Sent:* Wednesday, June 5, 2024 22:47 > *To:* user <user@flink.apache.org> > *Subject:* Force to commit kafka offset when stop a job. > > > When stopping a flink job that consuming kafka message, how to force it to > commit kafka offset > > Thanks, > Lei >
