You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by fh...@apache.org on 2019/09/23 10:30:45 UTC
[flink] branch master updated: [FLINK-14160][docs] Describe
--backpressure option for Operations Playground.
This is an automated email from the ASF dual-hosted git repository.
fhueske pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new c83c186 [FLINK-14160][docs] Describe --backpressure option for Operations Playground.
c83c186 is described below
commit c83c18671bc0056a341877f312ba293ae5811953
Author: David Anderson <da...@alpinegizmo.com>
AuthorDate: Sat Sep 21 10:51:02 2019 +0200
[FLINK-14160][docs] Describe --backpressure option for Operations Playground.
This closes #9739.
---
.../docker-playgrounds/flink-operations-playground.md | 17 ++++++++++++++---
.../flink-operations-playground.zh.md | 17 ++++++++++++++---
2 files changed, 28 insertions(+), 6 deletions(-)
diff --git a/docs/getting-started/docker-playgrounds/flink-operations-playground.md b/docs/getting-started/docker-playgrounds/flink-operations-playground.md
index 38a0848..c9f7675 100644
--- a/docs/getting-started/docker-playgrounds/flink-operations-playground.md
+++ b/docs/getting-started/docker-playgrounds/flink-operations-playground.md
@@ -136,7 +136,7 @@ will show you how to interact with the Flink Cluster and demonstrate some of Fli
### Flink WebUI
-The most natural starting point to observe your Flink Cluster is the Web UI exposed under
+The most natural starting point to observe your Flink Cluster is the WebUI exposed under
[http://localhost:8081](http://localhost:8081). If everything went well, you'll see that the cluster initially consists of
one TaskManager and executes a Job called *Click Event Count*.
@@ -802,8 +802,8 @@ TaskManager metrics);
## Variants
-You might have noticed that the *Click Event Count* was always started with `--checkpointing` and
-`--event-time` program arguments. By omitting these in the command of the *client* container in the
+You might have noticed that the *Click Event Count* application was always started with `--checkpointing`
+and `--event-time` program arguments. By omitting these in the command of the *client* container in the
`docker-compose.yaml`, you can change the behavior of the Job.
* `--checkpointing` enables [checkpoint]({{ site.baseurl }}/internals/stream_checkpointing.html),
@@ -815,3 +815,14 @@ lost.
Job. When disabled, the Job will assign events to windows based on the wall-clock time instead of
the timestamp of the `ClickEvent`. Consequently, the number of events per window will not be exactly
one thousand anymore.
+
+The *Click Event Count* application also has another option, turned off by default, that you can
+enable to explore the behavior of this job under backpressure. You can add this option in the
+command of the *client* container in `docker-compose.yaml`.
+
+* `--backpressure` adds an additional operator into the middle of the job that causes severe backpressure
+during even-numbered minutes (e.g., during 10:12, but not during 10:13). This can be observed by
+inspecting various [network metrics]({{ site.baseurl }}/monitoring/metrics.html#default-shuffle-service)
+such as `outputQueueLength` and `outPoolUsage`, and/or by using the
+[backpressure monitoring]({{ site.baseurl }}/monitoring/back_pressure.html#monitoring-back-pressure)
+available in the WebUI.
\ No newline at end of file
diff --git a/docs/getting-started/docker-playgrounds/flink-operations-playground.zh.md b/docs/getting-started/docker-playgrounds/flink-operations-playground.zh.md
index 38a0848..c9f7675 100644
--- a/docs/getting-started/docker-playgrounds/flink-operations-playground.zh.md
+++ b/docs/getting-started/docker-playgrounds/flink-operations-playground.zh.md
@@ -136,7 +136,7 @@ will show you how to interact with the Flink Cluster and demonstrate some of Fli
### Flink WebUI
-The most natural starting point to observe your Flink Cluster is the Web UI exposed under
+The most natural starting point to observe your Flink Cluster is the WebUI exposed under
[http://localhost:8081](http://localhost:8081). If everything went well, you'll see that the cluster initially consists of
one TaskManager and executes a Job called *Click Event Count*.
@@ -802,8 +802,8 @@ TaskManager metrics);
## Variants
-You might have noticed that the *Click Event Count* was always started with `--checkpointing` and
-`--event-time` program arguments. By omitting these in the command of the *client* container in the
+You might have noticed that the *Click Event Count* application was always started with `--checkpointing`
+and `--event-time` program arguments. By omitting these in the command of the *client* container in the
`docker-compose.yaml`, you can change the behavior of the Job.
* `--checkpointing` enables [checkpoint]({{ site.baseurl }}/internals/stream_checkpointing.html),
@@ -815,3 +815,14 @@ lost.
Job. When disabled, the Job will assign events to windows based on the wall-clock time instead of
the timestamp of the `ClickEvent`. Consequently, the number of events per window will not be exactly
one thousand anymore.
+
+The *Click Event Count* application also has another option, turned off by default, that you can
+enable to explore the behavior of this job under backpressure. You can add this option in the
+command of the *client* container in `docker-compose.yaml`.
+
+* `--backpressure` adds an additional operator into the middle of the job that causes severe backpressure
+during even-numbered minutes (e.g., during 10:12, but not during 10:13). This can be observed by
+inspecting various [network metrics]({{ site.baseurl }}/monitoring/metrics.html#default-shuffle-service)
+such as `outputQueueLength` and `outPoolUsage`, and/or by using the
+[backpressure monitoring]({{ site.baseurl }}/monitoring/back_pressure.html#monitoring-back-pressure)
+available in the WebUI.
\ No newline at end of file