wuchong commented on a change in pull request #9805: [FLINK-11635][docs-zh] translate dev/stream/state/checkpointing into Chinese URL: https://github.com/apache/flink/pull/9805#discussion_r334219286
########## File path: docs/dev/stream/state/checkpointing.zh.md ########## @@ -173,30 +165,26 @@ Some more parameters and/or defaults may be set via `conf/flink-conf.yaml` (see ## Selecting a State Backend -Flink's [checkpointing mechanism]({{ site.baseurl }}/internals/stream_checkpointing.html) stores consistent snapshots -of all the state in timers and stateful operators, including connectors, windows, and any [user-defined state](state.html). -Where the checkpoints are stored (e.g., JobManager memory, file system, database) depends on the configured -**State Backend**. - -By default, state is kept in memory in the TaskManagers and checkpoints are stored in memory in the JobManager. For proper persistence of large state, -Flink supports various approaches for storing and checkpointing state in other state backends. The choice of state backend can be configured via `StreamExecutionEnvironment.setStateBackend(…)`. +Flink 的 [checkpointing mechanism]({{ site.baseurl }}/zh/internals/stream_checkpointing.html) 存储在定时器与状态操作里的持久化快照, +包括连接器(connectors),窗口(windows)以及任何用户[自定义的状态](state.html) +checkpoint 存储在那里取决于所配置的 **State Backend**(比如 JobManager memory、 file system、 database)。 -See [state backends]({{ site.baseurl }}/ops/state/state_backends.html) for more details on the available state backends and options for job-wide and cluster-wide configuration. +默认情况下,状态是保持在 TaskManagers 的内存中,checkpoint 保存在 JobManager 的内存中。为了体量大的状态的能完全恰当的持久化, +Flink 支持各种各样的途径去存储,来 checkpoint 状态到其他的 state backends。通过 `StreamExecutionEnvironment.setStateBackend(…)` 来配置所选的 state backends。 +阅读 [state backends]({{ site.baseurl }}/zh/ops/state/state_backends.html) 来查看在可用 state backends 上的更多细节,选择 job范围 与 集群返回 的配置。 -## State Checkpoints in Iterative Jobs +## 在 Iterative Jobs 中的状态 checkpoint Review comment: ```suggestion ## Iterative Jobs 中的状态 和 checkpoint ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services