KarmaGYZ commented on a change in pull request #11401: [FLINK-15991][doc][zh]
Translate memory configuration docs into Chinese.
URL: https://github.com/apache/flink/pull/11401#discussion_r392809260
##########
File path: docs/ops/memory/mem_migration.zh.md
##########
@@ -121,116 +117,105 @@ The following options are deprecated but if they are
still used they will be int
</tbody>
</table>
-Although, the network memory configuration has not changed too much it is
recommended to verify its configuration.
-It can change if other memory components have new sizes, e.g. the total memory
which the network can be a fraction of.
-See also [new detailed memory model](mem_detail.html).
+尽管网络内存的配置参数没有发生太多变化，我们仍建议您检查其配置结果。
+网络内存的大小可能会受到其他内存部分大小变化的影响，例如总内存变化时，根据占比计算出的网络内存也可能发生变化。
+请参考[内存模型详解](mem_detail.html)。
-The container cut-off configuration options,
[`containerized.heap-cutoff-ratio`](config.html#containerized-heap-cutoff-ratio)
-and
[`containerized.heap-cutoff-min`](config.html#containerized-heap-cutoff-min),
have no effect for task manager processes anymore
-but they still have the same semantics for the job manager process. See also
[how to migrate container cut-off](#container-cut-off-memory).
+容器切除（Cut-Off）内存相关的配置参数（[`containerized.heap-cutoff-ratio`](config.html#containerized-heap-cutoff-ratio)
+和
[`containerized.heap-cutoff-min`](config.html#containerized-heap-cutoff-min)）将不再对
TaskExecutor 进程生效。
+对于 JobManager 进程，它们仍具有与此前相同的语义。
+请参考[如何升级容器切除内存](#容器切除cut-off内存)。
-## Total Memory (Previously Heap Memory)
+## 总内存（原堆内存）
-The previous options which were responsible for the total memory used by Flink
are `taskmanager.heap.size` or `taskmanager.heap.mb`.
-Despite their naming, they included not only JVM heap but also other off-heap
memory components. The options have been deprecated.
+在原本的内存配置方法中，用于指定用于 Flink 的总内存的配置参数是 `taskmanager.heap.size` 或
`taskmanager.heap.mb`。
+尽管这两个参数以“堆（Heap）”命名，实际上它们指定的内存既包含了 JVM 堆内存，也包含了其他堆外内存部分。
+这两个配置参数目前已被弃用。
-The Mesos integration also had a separate option with the same semantics:
`mesos.resourcemanager.tasks.mem` which has also been removed.
+Flink 在 Mesos 上还有另一个具有同样语义的配置参数 `mesos.resourcemanager.tasks.mem`，目前也已经被弃用。
-If the mentioned legacy options are used without specifying the corresponding
new options,
-they will be directly translated into the following new options:
-* Total Flink memory
([`taskmanager.memory.flink.size`](../config.html#taskmanager-memory-flink-size))
for standalone deployments
-* Total process memory
([`taskmanager.memory.process.size`](../config.html#taskmanager-memory-process-size))
for containerized deployments (Yarn or Mesos)
+如果配置了上述弃用的参数，同时又没有配置与之对应的新配置参数，那它们将按如下规则对应到新的配置参数。
+* 独立部署模式（Standalone Deployment）下：Flink
总内存（[`taskmanager.memory.flink.size`](../config.html#taskmanager-memory-flink-size)）
+* 容器化部署模式（Containerized
Deployement）下（Yarn、Mesos）：进程总内存（[`taskmanager.memory.process.size`](../config.html#taskmanager-memory-process-size)）
-It is also recommended to use these new options instead of the legacy ones as
they might be completely removed in the following releases.
+建议您尽早使用新的配置参数取代启用的配置参数，它们在今后的版本中可能会被彻底移除。
-See also [how to configure total memory now](mem_setup.html#配置总内存).
+请参考[如何配置总内存](mem_setup.html#配置总内存).
-## JVM Heap Memory
+## JVM 堆内存
-JVM heap memory previously consisted of the managed memory (if configured to
be on-heap) and the rest
-which included any other usages of heap memory. This rest was always
implicitly derived as the remaining part of the total memory,
-see also [how to migrate managed memory](#managed-memory).
+此前，JVM 堆空间由托管内存（仅在配置为堆上时）及 Flink 用到的所有其他堆内存组成。
+这里的其他堆内存是由总内存减去所有其他非堆内存得到的。
+请参考[如何升级托管内存](#托管内存)。
-Now, if only *total Flink memory* or *total process memory* is configured,
then the JVM heap is also derived as the rest of
-what is left after subtracting all other components from the total memory, see
also [how to configure total memory](mem_setup.html#配置总内存).
+现在，如果仅配置了*Flink总内存*或*进程总内存*，JVM 的堆空间依然是根据总内存减去所有其他非堆内存得到的。
+请参考[如何配置总内存](mem_setup.html#配置总内存)。
-Additionally, you can now have more direct control over the JVM heap assigned
to the operator tasks
-([`taskmanager.memory.task.heap.size`](../config.html#taskmanager-memory-task-heap-size)),
-see also [Task (Operator) Heap Memory](mem_setup.html#任务算子堆内存).
-The JVM heap memory is also used by the heap state backends
([MemoryStateBackend](../state/state_backends.html#the-memorystatebackend)
-or [FsStateBackend](../state/state_backends.html#the-fsstatebackend)) if it is
chosen for streaming jobs.
+此外，你现在可以更直接地控制用于任务和算子的 JVM
的堆内存（[`taskmanager.memory.task.heap.size`](../config.html#taskmanager-memory-task-heap-size)），详见[任务堆内存](mem_setup.html#任务算子堆内存)。
+如果流处理作业选择使用 Heap State
Backend（[MemoryStateBackend](../state/state_backends.html#the-memorystatebackend)
+或 [FsStateBackend](../state/state_backends.html#the-fsstatebackend)），那么它同样需要使用
JVM 堆内存。
-A part of the JVM heap is now always reserved for Flink framework
-([`taskmanager.memory.framework.heap.size`](../config.html#taskmanager-memory-framework-heap-size)).
-See also [Framework memory](mem_detail.html#框架内存).
+Flink 现在总是会预留一部分 JVM
堆内存供框架使用（[`taskmanager.memory.framework.heap.size`](../config.html#taskmanager-memory-framework-heap-size)）。
+请参考[框架内存](mem_detail.html#框架内存)。
-## Managed Memory
+## 托管内存
-See also [how to configure managed memory now](mem_setup.html#托管内存).
+请参考[如何配置托管内存](mem_setup.html#托管内存)。
-### Explicit Size
+### 明确的大小
-The previous option to configure managed memory size
(`taskmanager.memory.size`) was renamed to
-[`taskmanager.memory.managed.size`](../config.html#taskmanager-memory-managed-size)
and deprecated.
-It is recommended to use the new option because the legacy one can be removed
in future releases.
+原本用于指定明确的托管内存大小的配置参数（`taskmanager.memory.size`）已被弃用，与它具有相同语义的新配置参数为
[`taskmanager.memory.managed.size`](../config.html#taskmanager-memory-managed-size)。
+建议使用新的配置参数，原本的配置参数在今后的版本中可能会被彻底移除。
-### Fraction
+### 占比
-If not set explicitly, the managed memory could be previously specified as a
fraction (`taskmanager.memory.fraction`)
-of the total memory minus network memory and container cut-off (only for
[Yarn](../deployment/yarn_setup.html) and
-[Mesos](../deployment/mesos.html) deployments). This option has been
completely removed and will have no effect if still used.
-Please, use the new option
[`taskmanager.memory.managed.fraction`](../config.html#taskmanager-memory-managed-fraction)
instead.
-This new option will set the [managed memory](mem_setup.html#托管内存) to the
specified fraction of the
-[total Flink memory](mem_setup.html#配置总内存) if its size is not set explicitly by
-[`taskmanager.memory.managed.size`](../config.html#taskmanager-memory-managed-size).
+此前，如果不指定明确的大小，也可以将托管内存配置为占用总内存减去网络内存和容器切除内存（仅在
[Yarn](../deployment/yarn_setup.html) 和
+[Mesos](../deployment/mesos.html) 上）之后剩余部分的固定比例（`taskmanager.memory.fraction`）。
+该配置参数已经被彻底移除，配置它不会产生任何效果。
+请使用新的配置参数
[`taskmanager.memory.managed.fraction`](../config.html#taskmanager-memory-managed-fraction)。
+在未通过
[`taskmanager.memory.managed.size`](../config.html#taskmanager-memory-managed-size)
指定明确大小的情况下，新的配置参数将指定[托管内存](mem_setup.html#托管内存)在 [Flink
总内存](mem_setup.html#配置总内存)中的所占比例。
-### RocksDB state
+### RocksDB State Backend
-If the
[RocksDBStateBackend](../state/state_backends.html#the-rocksdbstatebackend) is
chosen for a streaming job,
-its native memory consumption should now be accounted for in [managed
memory](mem_setup.html#托管内存).
-The RocksDB memory allocation is limited by the [managed
memory](mem_setup.html#托管内存) size.
-This should prevent the killing of containers on
[Yarn](../deployment/yarn_setup.html) or [Mesos](../deployment/mesos.html).
-You can disable the RocksDB memory control by setting
[state.backend.rocksdb.memory.managed](../config.html#state-backend-rocksdb-memory-managed)
-to `false`. See also [how to migrate container
cut-off](#container-cut-off-memory).
+流处理作业如果选择使用
[RocksDBStateBackend](../state/state_backends.html#the-rocksdbstatebackend)，它使用的本地内存现在也被归为[托管内存](mem_setup.html#托管内存)。
Review comment:
Broken link.
----------------------------------------------------------------
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
