Better wording thanks to Andrea Selva

Fixes #11685
This commit is contained in:
Luca Belluccini 2020-03-13 12:01:13 +01:00 committed by Karen Metts
parent 9d789292f3
commit bd7d5b9b0f

View file

@ -152,7 +152,7 @@ Here is an example of this scenario using the output isolator pattern.
In this architecture, each stage has its own queue with its own tuning and settings. Note that this approach uses up to three times as much disk space and incurs three times as much serialization/deserialization cost as a single pipeline. In this architecture, each stage has its own queue with its own tuning and settings. Note that this approach uses up to three times as much disk space and incurs three times as much serialization/deserialization cost as a single pipeline.
If one or both persistent queues of the downstream pipelines (in the example above, `buffered-es` and `buffered-http`) are full, then the upstream pipeline (in the example above, `intake`) will receive backpressure. Once the persistent queue of the upstream pipeline becomes full, both outputs will stop. If any of the persistent queues of the downstream pipelines (in the example above, `buffered-es` and `buffered-http`) become full, both outputs will stop.
[[forked-path-pattern]] [[forked-path-pattern]]
===== The forked path pattern ===== The forked path pattern