Hi Hangxiang,
Thanks for providing me the steps to check if the checkpointing is getting
triggered on failure recovery. I will follow them and respond back in case
of any issues.
Thanks,
Elakiya
On Sat, Sep 30, 2023 at 2:34 PM Hangxiang Yu wrote:
> Hi, Elakiya.
>
> I think you could check :
>
Hi, Elakiya.
I think you could check :
1. The TaskManager Log to figure out whether the job is restoring from
an existing checkpoint and the restoring checkpoint path.
2. Or you could check the checkpoint ID when you restart your job (If
not restoring from a checkpoint, it starts from
Hi Feng,
Thanks for your response.
1. We have configured checkpointing to upload to a s3 location, also we see
metadata files getting created in the s3 location. But we are unsure if the
job is getting triggered from that checkpoint in case of failure. Is there
a possible way to test this. Also d
Hi Elakiya
1. You can confirm if the checkpoint for the task has been triggered
normally?
2. Also, If you stop the job, you need to use "STOP WITH SAVEPOINT" and
specify the path to the savepoint when starting the Flink job for recovery.
This is necessary to continue consuming from the historical
Hi team,
I have a Kafka topic named employee which uses confluent avro schema and
will emit the payload as below:
{
"id": "emp_123456",
"employee": {
"id": "123456",
"name": "sampleName"
}
}
I am using the upsert-kafka connector to consume the events from the above
Kafka topic as below using the F
