Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/2342#discussion_r74918068
--- Diff: docs/setup/config.md ---
@@ -285,7 +285,7 @@ of the JobManager, because the same ActorSystem is
used. Its not possible to use
## High Availability Mode
-- `recovery.mode`: (Default 'standalone') Defines the recovery mode used
for the cluster execution. Currently, Flink supports the 'standalone' mode
where only a single JobManager runs and no JobManager state is checkpointed.
The high availability mode 'zookeeper' supports the execution of multiple
JobManagers and JobManager state checkpointing. Among the group of JobManagers,
ZooKeeper elects one of them as the leader which is responsible for the cluster
execution. In case of a JobManager failure, a standby JobManager will be
elected as the new leader and is given the last checkpointed JobManager state.
In order to use the 'zookeeper' mode, it is mandatory to also define the
`recovery.zookeeper.quorum` configuration value.
+- `high-availability`: (Default 'none') Defines the recovery mode used for
the cluster execution. Currently, Flink supports the 'none' mode where only a
single JobManager runs and no JobManager state is checkpointed. The high
availability mode 'zookeeper' supports the execution of multiple JobManagers
and JobManager state checkpointing. Among the group of JobManagers, ZooKeeper
elects one of them as the leader which is responsible for the cluster
execution. In case of a JobManager failure, a standby JobManager will be
elected as the new leader and is given the last checkpointed JobManager state.
In order to use the 'zookeeper' mode, it is mandatory to also define the
`recovery.zookeeper.quorum` configuration value. Previously this config was
named 'recovery.mode' and the default config was 'standalone'.
- `recovery.zookeeper.quorum`: Defines the ZooKeeper quorum URL which is
used to connet to the ZooKeeper cluster when the 'zookeeper' recovery mode is
selected
--- End diff --
Docs not updated (same for jobmanager_high_availability.md)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
