github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 22:57:16 -04:00
Code Issues Projects Releases Packages Wiki Activity

Add doc notes referencing queue isolation in multipipeline configurations

Browse source 
Fixes #8077
This commit is contained in:
Rob Bavey 2017-08-25 15:13:18 -04:00
parent ccb3b7978f
commit 369dfd9b24
1 changed files with 2 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/static/multiple-pipelines.asciidoc vendored
View file

@ -27,3 +27,5 @@ Using multiple pipelines is especially useful if your current configuration has
Having multiple pipelines in a single instance also allows these event flows to have different performance and durability parameters (for example, different settings for pipeline workers and persistent queues). This separation means that a blocked output in one pipeline won't exert backpressure in the other.
That said, it's important to take into account resource competition between the pipelines, given that the default values are tuned for a single pipeline. So, for example, consider reducing the number of pipeline workers used by each pipeline, because each pipeline will use 1 worker per CPU core by default.
Persistent queues and dead letter queues are isolated per pipeline, with their locations namespaced by the `pipeline.id` value.