From 2af381a3f1a88c51deae5f5ba0f88307c4f82128 Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Wed, 22 Sep 2021 15:55:40 -0400 Subject: [PATCH] Doc: Add topic and expand info for mem queue --- docs/index.asciidoc | 3 +++ docs/static/mem-queue.asciidoc | 10 ++++++++++ 2 files changed, 13 insertions(+) create mode 100644 docs/static/mem-queue.asciidoc diff --git a/docs/index.asciidoc b/docs/index.asciidoc index e58ea85314a..403efa1ff6e 100644 --- a/docs/index.asciidoc +++ b/docs/index.asciidoc @@ -178,6 +178,9 @@ include::static/filebeat-modules.asciidoc[] :edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/resiliency.asciidoc include::static/resiliency.asciidoc[] +:edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/mem-queue.asciidoc +include::static/mem-queue.asciidoc[] + :edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/persistent-queues.asciidoc include::static/persistent-queues.asciidoc[] diff --git a/docs/static/mem-queue.asciidoc b/docs/static/mem-queue.asciidoc new file mode 100644 index 00000000000..b29be1e260c --- /dev/null +++ b/docs/static/mem-queue.asciidoc @@ -0,0 +1,10 @@ +[[memory-queue]] +=== Memory queue + +By default, Logstash uses in-memory bounded queues between pipeline stages +(inputs → pipeline workers) to buffer events. The size of these in-memory +queues is fixed and not configurable. If Logstash experiences a temporary +machine failure, the contents of the in-memory queue will be lost. Temporary machine +failures are scenarios where Logstash or its host machine are terminated +abnormally but are capable of being restarted. +