hapihu commented on a change in pull request #16295:
URL: https://github.com/apache/flink/pull/16295#discussion_r664022249
##########
File path: docs/content.zh/docs/deployment/cli.md
##########
@@ -139,26 +134,25 @@ Waiting for response...
Savepoint '/tmp/flink-savepoints/savepoint-cca7bc-bb1e257f0dab' disposed.
```
-If you use custom state instances (for example custom reducing state or
RocksDB state), you have to
-specify the path to the program JAR with which the savepoint was triggered.
Otherwise, you will run
-into a `ClassNotFoundException`:
+如果使用自定义状态实例（例如自定义 reducing 状态或 RocksDB 状态），则必须指定触发 savepoint 的 JAR
程序路径。否则，会遇到 `ClassNotFoundException` 异常 ：
+
```bash
$ ./bin/flink savepoint \
--dispose <savepointPath> \
--jarfile <jarFile>
```
-Triggering the savepoint disposal through the `savepoint` action does not only
remove the data from
-the storage but makes Flink clean up the savepoint-related metadata as well.
+通过 `savepoint` 操作触发 savepoint 废弃，不仅会将数据从存储中删除，还会使 Flink 清理与 savepoint 相关的元数据。
+
+<a name="terminating-a-savepoint"> </a>
-### Terminating a Job
+### 终止作业
-#### Stopping a Job Gracefully Creating a Final Savepoint
+<a name="stopping-a-job-gracefully-creating-a-final-savepoint"> </a>
-Another action for stopping a job is `stop`. It is a more graceful way of
stopping a running streaming
-job as the `stop` flows from source to sink. When the user requests to stop a
job, all sources will
-be requested to send the last checkpoint barrier that will trigger a
savepoint, and after the successful
-completion of that savepoint, they will finish by calling their `cancel()`
method.
+#### 优雅地终止作业并创建最终 Savepoint
+
+终止作业运行的操作是 `stop`。`stop` 操作停止从 source 到 sink 的作业流，是一种更优雅的终止方式。当用户请求终止一项作业时，所有的
sources 将被要求发送最后的 checkpoint 障碍，这会触发创建 checkpoint ，在成功完成 checkpoint 的创建后，Flink
会调用 `cancel()` 方法来终止作业。
Review comment:
ok, thank you.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
