Github user alpinegizmo commented on a diff in the pull request:
https://github.com/apache/flink/pull/5928#discussion_r184959202
--- Diff: docs/dev/stream/state/checkpointing.md ---
@@ -137,11 +137,9 @@ Some more parameters and/or defaults may be set via
`conf/flink-conf.yaml` (see
- `jobmanager`: In-memory state, backup to JobManager's/ZooKeeper's
memory. Should be used only for minimal state (Kafka offsets) or testing and
local debugging.
- `filesystem`: State is in-memory on the TaskManagers, and state
snapshots are stored in a file system. Supported are all filesystems supported
by Flink, for example HDFS, S3, ...
-- `state.backend.fs.checkpointdir`: Directory for storing checkpoints in a
Flink supported filesystem. Note: State backend must be accessible from the
JobManager, use `file://` only for local setups.
+- `state.checkpoints.dir`: The target directory for storing checkpoints
data files and meta data of [externalized checkpoints]({{ site.baseurl
}}/ops/state/checkpoints.html#externalized-checkpoints) in a Flink supported
filesystem. Note: State backend must be accessible from the JobManager, use
`file://` only for local setups.
--- End diff --
This seems potentially misleading -- isn't it okay to use a `file://` URI
in the case of a distributed filesystem that is mounted at the same mount point
across the cluster?
---
