This is an automated email from the ASF dual-hosted git repository.
nkruber pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 29df42b3e79e6dc2b6af02ec2d947a56ee6f0ab9
Author: Piotr Nowojski <piotr.nowoj...@gmail.com>
AuthorDate: Tue Jul 30 14:15:57 2019 +0200
[Blog] Change wording in Flink Network Stack Vol. 2
---
_posts/2019-07-23-flink-network-stack-2.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_posts/2019-07-23-flink-network-stack-2.md
b/_posts/2019-07-23-flink-network-stack-2.md
index abf97a9..4821269 100644
--- a/_posts/2019-07-23-flink-network-stack-2.md
+++ b/_posts/2019-07-23-flink-network-stack-2.md
@@ -249,7 +249,7 @@ Please note that, as of Flink 1.8 and 1.9, `numBuffersOut`
only increases for bu
Assuming that you identified where the source of backpressure — a bottleneck —
is located, the next step is to analyse why this is happening. Below, we list
some potential causes of backpressure from the more basic to the more complex
ones. We recommend to check the basic causes first, before diving deeper on the
more complex ones and potentially drawing false conclusions.
-Please also recall that backpressure might be temporary and the result of a
load spike, checkpointing, or a job restart with a data backlog waiting to be
processed. If backpressure is temporary, you should simply ignore it.
Alternatively, keep in mind that the process of analysing and solving the issue
can be affected by the intermittent nature of your bottleneck. Having said
that, here are a couple of things to check.
+Please also recall that backpressure might be temporary and the result of a
load spike, checkpointing, or a job restart with a data backlog waiting to be
processed. In that case, you can often just ignore it. Alternatively, keep in
mind that the process of analysing and solving the issue can be affected by the
intermittent nature of your bottleneck. Having said that, here are a couple of
things to check.
#### System Resources
