Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
statefun-3.2.0
-
None
-
None
Description
When running a Stateful Functions applications, if the stop[1] command is executed, the client throws a FlinkException with the following stack trace where 953498833da99ec437758b49b7d5befd is the specific job id:
The program finished with the following exception:org.apache.flink.util.FlinkException: Could not stop with a savepoint job "953498833da99ec437758b49b7d5befd".
at org.apache.flink.client.cli.CliFrontend.lambda$stop$5(CliFrontend.java:581)
at org.apache.flink.client.cli.CliFrontend.runClusterAction(CliFrontend.java:1002)
at org.apache.flink.client.cli.CliFrontend.stop(CliFrontend.java:569)
at org.apache.flink.client.cli.CliFrontend.parseAndRun(CliFrontend.java:1069)
at org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1132)
at org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:28)
at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1132)
Caused by: java.util.concurrent.TimeoutException
at java.base/java.util.concurrent.CompletableFuture.timedGet(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.get(Unknown Source)
at org.apache.flink.client.cli.CliFrontend.lambda$stop$5(CliFrontend.java:579)
... 6 more
How to reproduce:
- Follow the README[2] of the k8s deployment example of the flink-statefun-playground project to have a running application
- Open the Flink UI that is started to get the JOB_ID
- Detect the STATEFUN_MASTER_POD_NAME by running: kubectl get pods --namespace statefun
- Start a shell into the statefun-master pod by issuing the: kubectl exec -it --namespace statefun $STATEFUN_MASTER_POD_NAME – /bin/bash
- Run the stop command: ./bin/flink stop --savepointPath /tmp/flink-savepoints $JOB_ID
[2]: https://github.com/apache/flink-statefun-playground/blob/main/deployments/k8s/README.md