[flink] branch release-1.14 updated: [FLINK-24777][docs] Correct description of 'Processed (persisted) in-flight data'

[ta...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tangyun pushed a commit to branch release-1.14
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.14 by this push:
     new ef0e17a  [FLINK-24777][docs] Correct description of 'Processed (persisted) in-flight data'
ef0e17a is described below

commit ef0e17ad6319175ce0054fc3c4db14b78e690dd6
Author: camilesing <ca...@gmail.com>
AuthorDate: Fri Nov 5 00:14:59 2021 +0800

    [FLINK-24777][docs] Correct description of 'Processed (persisted) in-flight data'
    
    This closes #17686.
---
 docs/content.zh/docs/ops/monitoring/checkpoint_monitoring.md | 3 +--
 docs/content/docs/ops/monitoring/checkpoint_monitoring.md    | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/content.zh/docs/ops/monitoring/checkpoint_monitoring.md b/docs/content.zh/docs/ops/monitoring/checkpoint_monitoring.md
index 0335875..06d072c 100644
--- a/docs/content.zh/docs/ops/monitoring/checkpoint_monitoring.md
+++ b/docs/content.zh/docs/ops/monitoring/checkpoint_monitoring.md
@@ -73,8 +73,7 @@ Checkpoint 历史记录保存有关最近触发的 checkpoint 的统计信息，
 - **Latest Acknowledgement**：JobManager 接收到任何 subtask 的最新确认的时间（如果尚未收到确认，则不适用）。
 - **End to End Duration**：从触发时间戳到最后一次确认的持续时间（如果还没有收到确认，则不适用）。完整 checkpoint 的端到端持续时间由确认 checkpoint 的最后一个 subtask 确定。这个时间通常大于单个 subtask 实际 checkpoint state 所需的时间。
 - **Checkpointed Data Size**：所有已确认的 subtask 的 checkpoint 的数据大小。如果启用了增量 checkpoint，则此值为 checkpoint 数据的增量大小。
-- **Processed in-flight data**：在 checkpoint alignment 期间（从接收第一个和最后一个 checkpoint barrier 之间的时间）对所有已确认的 subtask 处理的大约字节数。
-- **Persisted in-flight data**：在 checkpoint alignment 期间（从接收第一个和最后一个 checkpoint barrier 之间的时间）对所有已确认的 subtask 持久化的字节数。仅当启用 unaligned checkpoint 时，此值大于 0。
+- **Processed (persisted) in-flight data**：在 checkpoint 对齐期间（从接收第一个和最后一个 checkpoint barrier 之间的时间）所有已确认的 subtask 处理/持久化 的大约字节数。如果启用了 unaligned checkpoint，持久化的字节数可能会大于0。
 
 对于 subtask，有两个更详细的统计信息可用。
 
diff --git a/docs/content/docs/ops/monitoring/checkpoint_monitoring.md b/docs/content/docs/ops/monitoring/checkpoint_monitoring.md
index 2e9915f..f5cda06 100644
--- a/docs/content/docs/ops/monitoring/checkpoint_monitoring.md
+++ b/docs/content/docs/ops/monitoring/checkpoint_monitoring.md
@@ -64,8 +64,7 @@ Note that for failed checkpoints, metrics are updated on a best efforts basis an
 - **Latest Acknowledgement**: The time when the latest acknowledgement for any subtask was received at the JobManager (or n/a if no acknowledgement received yet).
 - **End to End Duration**: The duration from the trigger timestamp until the latest acknowledgement (or n/a if no acknowledgement received yet). This end to end duration for a complete checkpoint is determined by the last subtask that acknowledges the checkpoint. This time is usually larger than single subtasks need to actually checkpoint the state.
 - **Checkpointed Data Size**: The checkpointed data size over all acknowledged subtasks. If incremental checkpointing is enabled this value is the checkpointed data size delta.
-- **Processed in-flight data**: The approximate number of bytes processed during the alignment (time between receiving the first and the last checkpoint barrier) over all acknowledged subtasks.
-- **Persisted in-flight data**: The number of bytes persisted during the alignment (time between receiving the first and the last checkpoint barrier) over all acknowledged subtasks. This is > 0 only if the unaligned checkpoints are enabled.
+- **Processed (persisted) in-flight data**: The approximate number of bytes processed/persisted during the alignment (time between receiving the first and the last checkpoint barrier) over all acknowledged subtasks. Persisted data could be larger than zero only if the unaligned checkpoints are enabled.
 
 For subtasks there are a couple of more detailed stats available.