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 55198a2d405a6cc0848d165c0f8b8708a6fc2c81
Author: Piotr Nowojski <piotr.nowoj...@gmail.com>
AuthorDate: Tue Jul 30 14:16:04 2019 +0200
Rebuild website
---
content/2019/07/23/flink-network-stack-2.html | 4 ++--
content/blog/feed.xml | 2 +-
content/contributing/contribute-code.html | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/2019/07/23/flink-network-stack-2.html
b/content/2019/07/23/flink-network-stack-2.html
index 3601198..2955939 100644
--- a/content/2019/07/23/flink-network-stack-2.html
+++ b/content/2019/07/23/flink-network-stack-2.html
@@ -108,7 +108,7 @@
<a class="dropdown-toggle" data-toggle="dropdown"
href="#">Documentation<span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a
href="https://ci.apache.org/projects/flink/flink-docs-release-1.8";
target="_blank">1.8 (Latest stable release) <small><span class="glyphicon
glyphicon-new-window"></span></small></a></li>
- <li><a
href="https://ci.apache.org/projects/flink/flink-docs-master";
target="_blank">1.9 (Snapshot) <small><span class="glyphicon
glyphicon-new-window"></span></small></a></li>
+ <li><a
href="https://ci.apache.org/projects/flink/flink-docs-master";
target="_blank">Master (Latest Snapshot) <small><span class="glyphicon
glyphicon-new-window"></span></small></a></li>
</ul>
</li>
@@ -459,7 +459,7 @@ Please note that, as of Flink 1.8 and 1.9,
<code>numBuffersOut</code> only incre
<p>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.</p>
- <p>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.</p>
+ <p>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.</p>
<h4 id="system-resources">System Resources</h4>
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index cc8dfe3..2c6f2e5 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -294,7 +294,7 @@ Please note that, as of Flink 1.8 and 1.9,
<code>numBuffersOut</code>
<p>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.</p>
- <p>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.</p>
+ <p>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.</p>
<h4 id="system-resources">System Resources</h4>
diff --git a/content/contributing/contribute-code.html
b/content/contributing/contribute-code.html
index 92e873e..f1212db 100644
--- a/content/contributing/contribute-code.html
+++ b/content/contributing/contribute-code.html
@@ -288,7 +288,7 @@
<div class="panel-body">
<h2><span class="number">3</span><a href="#review">Review</a></h2>
<p>Open a pull request and work with the reviewer.</p>
- <p><b>Pull requests belonging to unassigned Jira tickets will not be
reviewed or merged by the community.</b></p>
+ <p><b>Pull requests belonging to unassigned Jira tickets or not
authored by assignee will not be reviewed or merged by the community.</b></p>
</div>
</div>
</div>
