klion26 commented on a change in pull request #8943:
[FLINK-11637][doc-zh]Translate Checkpoints page into Chinese
URL: https://github.com/apache/flink/pull/8943#discussion_r299785669
##########
File path: docs/ops/state/checkpoints.zh.md
##########
@@ -26,69 +26,49 @@ under the License.
* toc
{:toc}
-## Overview
+## 概述
+checkpoint使Flink的状态具有良好的容错性，通过checkpoint机制，Flink可以对作业的状态和计算位置进行恢复，因此Flink作业具备高容错执行语义。
-Checkpoints make state in Flink fault tolerant by allowing state and the
-corresponding stream positions to be recovered, thereby giving the application
-the same semantics as a failure-free execution.
+参考[Checkpointing]({{ site.baseurl
}}/dev/stream/state/checkpointing.html)查看如何在Flink程序中开启和配置checkpoint。
-See [Checkpointing]({{ site.baseurl }}/dev/stream/state/checkpointing.html)
for how to enable and
-configure checkpoints for your program.
+## 保留Checkpoint
-## Retained Checkpoints
-
-Checkpoints are by default not retained and are only used to resume a
-job from failures. They are deleted when a program is cancelled.
-You can, however, configure periodic checkpoints to be retained.
-Depending on the configuration these *retained* checkpoints are *not*
-automatically cleaned up when the job fails or is canceled.
-This way, you will have a checkpoint around to resume from if your job fails.
+checkpoint在默认的情况下仅用于恢复失败的作业，并不作保留，当程序取消时checkpoint就会被删除。当然，你可以配置周期性的策略来保留checkpoint。根据以下配置，这些保留的checkpoint在作业失败或取消时不会自动清除。这样，你就可以使用该checkpoint来恢复失败的作业。
{% highlight java %}
CheckpointConfig config = env.getCheckpointConfig();
config.enableExternalizedCheckpoints(ExternalizedCheckpointCleanup.RETAIN_ON_CANCELLATION);
{% endhighlight %}
-The `ExternalizedCheckpointCleanup` mode configures what happens with
checkpoints when you cancel the job:
-
-- **`ExternalizedCheckpointCleanup.RETAIN_ON_CANCELLATION`**: Retain the
checkpoint when the job is cancelled. Note that you have to manually clean up
the checkpoint state after cancellation in this case.
-
-- **`ExternalizedCheckpointCleanup.DELETE_ON_CANCELLATION`**: Delete the
checkpoint when the job is cancelled. The checkpoint state will only be
available if the job fails.
+`ExternalizedCheckpointCleanup`配置项定义了当作业取消时，对作业checkpoint的操作：
+-
**`ExternalizedCheckpointCleanup.RETAIN_ON_CANCELLATION`**：当作业取消时，保留作业的checkpoint。注意，这种情况下，需要手动清除该作业的checkpoint。
+-
**`ExternalizedCheckpointCleanup.DELETE_ON_CANCELLATION`**：当作业取消时，删除作业的checkpoint。仅当作业失败时，作业的checkpoint才会被启用。
-### Directory Structure
+### 目录结构
-Similarly to [savepoints](savepoints.html), a checkpoint consists
-of a meta data file and, depending on the state backend, some additional data
-files. The meta data file and data files are stored in the directory that is
-configured via `state.checkpoints.dir` in the configuration files,
-and also can be specified for per job in the code.
+与[savepoints](savepoints.html)相似，checkpoint由元数据文件、额外的数据文件（与state
backend相关）组成。可通过配置文件中“state.checkpoints.dir”配置项来指定元数据文件和数据文件的存储路径，另外也可以在代码中针对单个作业特别指定该配置项。
-#### Configure globally via configuration files
+#### 通过配置文件全局配置
{% highlight yaml %}
state.checkpoints.dir: hdfs:///checkpoints/
{% endhighlight %}
-#### Configure for per job when constructing the state backend
+#### 创建state backend对单个作业进行配置
{% highlight java %}
env.setStateBackend(new RocksDBStateBackend("hdfs:///checkpoints-data/"));
{% endhighlight %}
-### Difference to Savepoints
+### Checkpoint与Savepoint的区别
-Checkpoints have a few differences from [savepoints](savepoints.html). They
-- use a state backend specific (low-level) data format, may be incremental.
-- do not support Flink specific features like rescaling.
+checkpoint与[savepoints](savepoints.html)有一些区别，体现在他们：
+- 使用特定于state backend（低级）的数据格式，可能以增量方式存储。
+- 不支持Flink的特定功能，比如扩缩容。
-### Resuming from a retained checkpoint
+### 从checkpoint中恢复状态
Review comment:
```suggestion
### 从保留的 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
