You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@heron.apache.org by nw...@apache.org on 2019/01/07 18:48:12 UTC
[incubator-heron] branch master updated: Update backpressure
explanation in Heron architecture doc (#3145)
This is an automated email from the ASF dual-hosted git repository.
nwang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-heron.git
The following commit(s) were added to refs/heads/master by this push:
new 3ca8bfb Update backpressure explanation in Heron architecture doc (#3145)
3ca8bfb is described below
commit 3ca8bfbecca9d8c5f976f582b32eb10a9b11abb4
Author: Ning Wang <nw...@twitter.com>
AuthorDate: Mon Jan 7 10:48:07 2019 -0800
Update backpressure explanation in Heron architecture doc (#3145)
---
website/content/docs/concepts/architecture.md | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/website/content/docs/concepts/architecture.md b/website/content/docs/concepts/architecture.md
index 29ec426..c09f46e 100644
--- a/website/content/docs/concepts/architecture.md
+++ b/website/content/docs/concepts/architecture.md
@@ -148,10 +148,9 @@ SMs in containers **C** and **D**, which will lead to the socket buffers in
those containers filling up, which could lead to throughput collapse.
In a situation like this, Heron's back pressure mechanism will kick in. The **SM**
-in container **A** will send a message to all the other **SMs**. In response, the
-other **SMs** will examine the container's [physical
-plan](../topologies#physical-plan) and cut off inputs from spouts that feed
-bolt **B3** (in this case spout **S1**).
+in container **A** will send a message to all the other **SMs**, then all
+**SMs** will cut off inputs from local spouts and no new data will be accepted
+into the topology.
