Hey Min, when a Flink job recovers after a failure, the main method is not re-executed. The main method is only executed for the submission of the job. The JobManager executing the job is receiving the final job graph. On failure, the JobManager will restore the job based on the job graph. If you start a Flink job from scratch, it will use the current configuration. On a failure recovery, the Flink job will rely on the checkpoint.
Please let me know if your problem has been resolved with this information. If not, I need a bit more information on what you are trying to achieve, so that I can help you better. Best, Robert On Mon, Dec 2, 2019 at 10:12 AM <min....@ubs.com> wrote: > Many thanks for sending your reply. > > > > It is not for monitoring but for configuration. > > > > For a job starting from an empty status, we like to load the fresh > configurations. > > For a job recovering from a checkpoint, we like to rely on the checkpoint. > > > > Regards, > > > > Min > > > > *From:* vino yang [mailto:yanghua1...@gmail.com] > *Sent:* Montag, 2. Dezember 2019 10:09 > *To:* Tan, Min > *Cc:* user > *Subject:* [External] Re: Access to CheckpointStatsCounts > > > > Hi min, > > > > If it is only for monitoring purposes, you can just use checkpoint REST > API[1] to do this work. > > > > [1]: > https://ci.apache.org/projects/flink/flink-docs-release-1.9/monitoring/rest_api.html#jobs-jobid-checkpoints > > > > Best, > > Vino > > > > <min....@ubs.com> 于2019年12月2日周一 下午5:01写道： > > Hi, > > > > Just wonder how to access the CheckpointStatsCoutns from the main method > of a job? > > > > We need to detect if a job recovers from a checkpoint or starts from an > empty status. > > > > Regards, > > > > Min > >
