xiangforever2014 commented on PR #23253: URL: https://github.com/apache/flink/pull/23253#issuecomment-1820273335
@masteryhx Many thanks for your suggestion, and I have followed your advice to simplify the code. I have tested in my local machine, when triggering a detached savepoint, the CLI will return with a trigger id immediately, and I could use the trigger id to get the status of the savepoint by REST API [/jobs/:jobid/savepoints/:triggerid ](https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/ops/rest_api/#jobs-jobid-savepoints-triggerid). Triggering a savepoint vs. Triggering a detached savepoint: 1. Triggering a savepoint: from the picture, we could see that the CLI should wait for the savepoint to be finished, and it is very easy to cause a CLI timeout when the state of the job is huge.  2. Triggering a detached savepoint: the CLI returned with the trigger id immediately, and we could get the status of the savepoint by REST API.  - when the savepoint has not finished, we get  - once the savepoint finished, we get  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org