Job is "FAILED" state and hence Flink HA Removed the job graph from
zookeeper along with the state.
One thing is we can't completely rely on Flink HA for state restoring.
It will only until Job hasn't FAILED
If you want to recover Job even after Failure, you should do the following:
a) Use the
> Why do we want to restore from the savepoint taken the new Flink version
instead of the previous savepoint, is that we want to minimize the source
rewind?
You are exactly right. E.g. A user upgraded to the new version for a few
days and decided to roll back to the old version due to some
It seems like the JobManager is treating this as a job failure.
A FAILED JobStatus is a globally terminal state so everything gets deleted
with zookeeper HA.
https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/common/JobStatus.java#L39
Hi,
We are running Flink 1.9 in K8S. We used
https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/jobmanager_high_availability.html
to set high availability. We have a single master. We set max number of
retries for a task to 2. After task fails twice and then the job manager
Jeff Zhang created FLINK-18167:
--
Summary: Flink Job hangs there when one vertex is failed and
another is cancelled.
Key: FLINK-18167
URL: https://issues.apache.org/jira/browse/FLINK-18167
Project:
appleyuchi created FLINK-18166:
--
Summary: JAVA_HOME is not read from .bashrc when start flink
Key: FLINK-18166
URL: https://issues.apache.org/jira/browse/FLINK-18166
Project: Flink
Issue Type:
Xinyuan Liu created FLINK-18165:
---
Summary: When savingpoint is restored, select the checkpoint
directory and stateBackend
Key: FLINK-18165
URL: https://issues.apache.org/jira/browse/FLINK-18165
+1 (non-binding)
- signatures & hash, ok
- mvn clean install -Prun-e2e-tests on 1.8.0_77, ok
- source archives do not contains any binaries, ok
- version of POM files and Dockerfiles are correct, ok
---
Best,
Matt Wang
On 06/5/2020 16:58，Robert Metzger wrote：
Thanks a lot for creating this
Hi, Abdul.
Thank you for reaching out and for your interest in Google Season of Docs
(GSoD)!
We really appreciate it that you took the time to walk us through your
experience, as well as your previous contributions to open source. Even
though we are accepting applications from people with any
