It would be good if you could take a look at the Job-/TaskManager logs
to see whether the operation is making progress or whether an exception
has occurred.
Does the job stop eventually?
It could be that draining the jobs just takes longer than the client
timeout allows by default (60 seconds); you could try increasing that a
bit via the client.timeout option.
On 1/28/2021 3:30 AM, Marco Villalobos wrote:
When I try to stop with a savepoint, I usually get the error below. I
have not been able to create a single save point. Please advise.
I am using Flink 1.11.0
Draining job "ed51084378323a7d9fb1c4c97c2657df" with a savepoint.
------------------------------------------------------------
The program finished with the following exception:
org.apache.flink.util.FlinkException: Could not stop with a savepoint
job "ed51084378323a7d9fb1c4c97c2657df".
at
org.apache.flink.client.cli.CliFrontend.lambda$stop$5(CliFrontend.java:495)
at
org.apache.flink.client.cli.CliFrontend.runClusterAction(CliFrontend.java:864)
at org.apache.flink.client.cli.CliFrontend.stop(CliFrontend.java:487)
at
org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:931)
at
org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:992)
at
org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:30)
at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:992)
Caused by: java.util.concurrent.TimeoutException
at
java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)
at
org.apache.flink.client.cli.CliFrontend.lambda$stop$5(CliFrontend.java:493)
... 6 more
