Thank You it helped.
> On Apr 8, 2021, at 10:53 PM, Arvid Heise wrote:
>
>
> Hi Vijay,
>
> if you don't specify a checkpoint, then Flink assumes you want to start from
> scratch (e.g., you had a bug in your business logic and need to start
> completely without state).
>
> If there is any
Hi Vijay,
if you don't specify a checkpoint, then Flink assumes you want to start
from scratch (e.g., you had a bug in your business logic and need to start
completely without state).
If there is any failure and Flink restarts automatically, it will always
pick up from the latest checkpoint [1].
Thanks it was working fine with: bin/flink run -s
s3://bucketxx-app/flink/checkpoint/iv/f1ef373e27203907d2d568bca31e6556/chk-384/
\
On Thu, Apr 8, 2021 at 11:42 AM Vijayendra Yadav
wrote:
> Hi Arvid,
>
> Thanks for your response. I did not restart from the checkpoint. I assumed
> Flink would lo
Hi Arvid,
Thanks for your response. I did not restart from the checkpoint. I assumed
Flink would look for a checkpoint upon restart automatically.
*I should restart like below ?*
bin/flink run -s
s3://bucketxx-app/flink/checkpoint/iv/f1ef373e27203907d2d568bca31e6556/chk-384/
\
Thanks,
Vijay
O
Hi Vijay,
edit: After re-reading your message: are you sure that you restart from a
checkpoint/savepoint? If you just start the application anew and use LATEST
initial position, this is the expected bahvior.
--- original intended answer if you restart from checkpoint
this is definitively not the
Hi Team,
We are trying to make sure we are not losing data when KINESIS Consumer is
down.
Kinesis streaming Job which has following checkpointing properties:
*// checkpoint every X msecs
env.enableCheckpointing(Conf.getFlinkCheckpointInterval());*
*// enable externalized checkpoints whi
