Restarting from a checkpoint or savepoint in Business Automation Insights 18.0.0 and 18.0.1

In Business Automation Insights 18.0.0 and 18.0.1, you create savepoints by running the Kubernetes exec command and you update the property for path recovery.

About this task

At any time, you can create savepoints by running the exec command as shown below. If a job failure is preventing you from creating a savepoint, that is, if the flink savepoint command fails, you need to use the latest successful checkpoint. Because only the latest successful checkpoint is retained, and to prevent that checkpoint from being deleted while a new checkpoint is created, you must cancel the job. On cancellation, the latest checkpoint is retained. You can then restart the processing by using the Recovery Path property of each job submitter in the Helm release properties.

Procedure

To create a savepoint, run the exec command.
```
kubectl exec -it <my-release>-bai-flink-jobmanager-<id> -- flink savepoint <job-id>
```
You can find the <job-id> value in the Flink web interface. This command returns the path to the new savepoint in this format: /mnt/pv/savepoints/<savepoint-id>.
To cancel a job, select it in the Flink web interface and click Cancel on the job view page.
To see the latest successful checkpoint path in the Flink web interface, from the job view page, click the Checkpoints tab and then click More details.
The latest successful checkpoint is saved on this path: /mnt/pv/checkpoints/<job-id>/chk-<checkpoint-id>
To update the Recovery Path property, follow the procedure in Updating your Business Automation Insights deployment.
By default, you can restart a job from a same checkpoint or savepoint only once. This is a safety mechanism in case you forget to remove the value of the Recovery Path property. If you try to restart more than once, the job submitter falls into error state and returns a message such as Error: The savepoint <path/to/savepoint> was already used. The Job won't be run from there.

The job resumes processing from where it was when the specified checkpoint or savepoint was created.
Optional: If you really need to restart a job from the same checkpoint or savepoint more than once, first delete the /recovery/<job-name>/<savepoint-id> savepoint on the persistent volume (PV).