You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by tr...@apache.org on 2018/08/22 13:40:47 UTC
[flink] 05/05: [hotfix][docs] Document how to resume from a
savepoint with a job cluster on K8s
This is an automated email from the ASF dual-hosted git repository.
trohrmann pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
commit 6258a4c333ce9dba914621b13eac2f7d91f5cb72
Author: Till Rohrmann <tr...@apache.org>
AuthorDate: Thu Aug 16 19:56:47 2018 +0200
[hotfix][docs] Document how to resume from a savepoint with a job cluster on K8s
---
docs/ops/deployment/kubernetes.md | 5 ++---
flink-container/kubernetes/README.md | 7 +++++++
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/ops/deployment/kubernetes.md b/docs/ops/deployment/kubernetes.md
index 298e473..5244f5e 100644
--- a/docs/ops/deployment/kubernetes.md
+++ b/docs/ops/deployment/kubernetes.md
@@ -34,9 +34,8 @@ Please follow [Kubernetes' setup guide](https://kubernetes.io/docs/setup/) in or
If you want to run Kubernetes locally, we recommend using [MiniKube](https://kubernetes.io/docs/setup/minikube/).
<div class="alert alert-info" markdown="span">
- <strong>Note:</strong> If using MiniKube please make sure to execute `minikube ssh 'sudo ip link set docker0
- promisc on'` before deploying a Flink cluster. Otherwise Flink components are not able to self reference
- themselves through a Kubernetes service.
+ <strong>Note:</strong> If using MiniKube please make sure to execute `minikube ssh 'sudo ip link set docker0 promisc on'` before deploying a Flink cluster.
+ Otherwise Flink components are not able to self reference themselves through a Kubernetes service.
</div>
## Flink session cluster on Kubernetes
diff --git a/flink-container/kubernetes/README.md b/flink-container/kubernetes/README.md
index efba823..8a663f6 100644
--- a/flink-container/kubernetes/README.md
+++ b/flink-container/kubernetes/README.md
@@ -38,6 +38,13 @@ At last, you should start the task manager deployment:
`FLINK_IMAGE_NAME=<IMAGE_NAME> FLINK_JOB_PARALLELISM=<PARALLELISM> envsubst < task-manager-deployment.yaml.template | kubectl create -f -`
+## Resuming from a savepoint
+
+In order to resume from a savepoint, one needs to pass the savepoint path to the cluster entrypoint.
+This can be achieved by adding `"--fromSavepoint", "<SAVEPOINT_PATH>"` to the `args` field in the [job-cluster-job.yaml.template](job-cluster-job.yaml.template).
+Note that `<SAVEPOINT_PATH>` needs to be accessible from the `job-cluster-job` pod (e.g. adding it to the image or storing it on a DFS).
+Additionally one can specify `"--allowNonRestoredState"` to allow that savepoint state is skipped which cannot be restored.
+
## Interact with Flink job cluster
After starting the job cluster service, the web UI will be available under `<NODE_IP>:30081`.