MartijnVisser commented on a change in pull request #18110:
URL: https://github.com/apache/flink/pull/18110#discussion_r770299807
##########
File path: docs/content/docs/deployment/memory/network_mem_tuning.md
##########
@@ -114,7 +114,7 @@ Unlike the input buffer pool, the output buffer pool has
only one type of buffer
In order to avoid excessive data skew, the number of buffers for each
subpartition is limited by the
`taskmanager.network.memory.max-buffers-per-channel` setting.
-Like the input buffer pool, the configured amount of exclusive buffers and
floating buffers is only treated as recommended values. If there are not enough
buffers available, Flink can make progress with only a single exclusive buffer
per output subpartition and zero floating buffers.
+Unlike the input buffer pool, the configured amount of exclusive buffers and
floating buffers is only treated as recommended values. If there are not enough
buffers available, Flink can make progress with only a single exclusive buffer
per output subpartition and zero floating buffers.
Review comment:
```suggestion
The configured amount of exclusive buffers and floating buffers are only
treated as recommended values. If there are not enough buffers available, Flink
can make progress with only a single exclusive buffer per output subpartition
and zero floating buffers.
```
--
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]
