This is an automated email from the ASF dual-hosted git repository. pnowojski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/flink.git
commit f88d276bb4271cc5f1f52b6af68a5a7250f67c89 Author: Piotr Nowojski <[email protected]> AuthorDate: Tue Jun 21 17:12:07 2022 +0200 fixup! fixup! [FLINK-26762][docs] Document overdraft buffers --- docs/content.zh/docs/deployment/memory/network_mem_tuning.md | 4 ++-- docs/content/docs/deployment/memory/network_mem_tuning.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/content.zh/docs/deployment/memory/network_mem_tuning.md b/docs/content.zh/docs/deployment/memory/network_mem_tuning.md index 39527284814..b7e49d3218b 100644 --- a/docs/content.zh/docs/deployment/memory/network_mem_tuning.md +++ b/docs/content.zh/docs/deployment/memory/network_mem_tuning.md @@ -122,8 +122,8 @@ Flink 有多个本地缓冲区池 —— 每个输出和输入流对应一个。 For each output subtask can also request up to `taskmanager.network.memory.max-overdraft-buffers-per-gate` (by default 5) extra overdraft buffers. Those buffers are only used, if the subtask is backpressured -by downstream subtasks but the subtask can not gracefully pause its current process. This can happen -in situations like: +by downstream subtasks and the subtask requires more than a single network buffer to finish what its +currently doing. This can happen in situations like: - Serializing very large records, that do not fit into a single network buffer. - Flat Map like operator, that produces many output records per single input record. - Operators that output many records either periodically or on a reaction to some events (for diff --git a/docs/content/docs/deployment/memory/network_mem_tuning.md b/docs/content/docs/deployment/memory/network_mem_tuning.md index 00f8159e016..032fd3f5a17 100644 --- a/docs/content/docs/deployment/memory/network_mem_tuning.md +++ b/docs/content/docs/deployment/memory/network_mem_tuning.md @@ -124,8 +124,8 @@ Unlike the input buffer pool, the configured amount of exclusive buffers and flo For each output subtask can also request up to `taskmanager.network.memory.max-overdraft-buffers-per-gate` (by default 5) extra overdraft buffers. Those buffers are only used, if the subtask is backpressured -by downstream subtasks but the subtask can not gracefully pause its current process. This can happen -in situations like: +by downstream subtasks and the subtask requires more than a single network buffer to finish what its +currently doing. This can happen in situations like: - Serializing very large records, that do not fit into a single network buffer. - Flat Map like operator, that produces many output records per single input record. - Operators that output many records either periodically or on a reaction to some events (for
