You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (JIRA)" <ji...@apache.org> on 2019/04/26 06:31:00 UTC
[jira] [Assigned] (FLINK-12333) Add documentation around save point
with cancel lifecycle through REST
[ https://issues.apache.org/jira/browse/FLINK-12333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yun Tang reassigned FLINK-12333:
--------------------------------
Assignee: Yun Tang
> Add documentation around save point with cancel lifecycle through REST
> -----------------------------------------------------------------------
>
> Key: FLINK-12333
> URL: https://issues.apache.org/jira/browse/FLINK-12333
> Project: Flink
> Issue Type: Bug
> Components: Runtime / REST
> Affects Versions: 1.8.0
> Reporter: Vishal Santoshi
> Assignee: Yun Tang
> Priority: Minor
>
> Exit code 2 seen ( after 5 minutes ) when
> {code:java}
> curl --header "Content-Type: application/json" --request POST --data '{"target-directory":"***********","cancel-job":true}' https://***************/jobs/00000000000000000000000000000000/savepoints{code}
> It seems that when a REST call is
> "Triggered the cancel with savepoint command from via the REST call. This command is an asynchronous operation which produces a result (the savepoint path). In order to deliver asynchronous results to the caller, Flink waits before shutting down until they are delivered or until it times out after 5 minutes."
>
> That implies that one has to execute
> {code:java}
> curl --request GET https://**********/jobs/00000000000000000000000000000000/savepoints/[Request_id]
> {code}
> on the request_id returned by the first call ( within 5 minutes ) , for a clean exit ( code 0 )
>
> Please add this life cycle in flink documentation , in all probability here [https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jobs-jobid-savepoints]
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)