Doc: Add topic and expand info for mem queue

elastic · Sep 22, 2021 · 2af381a · 2af381a
1 parent 37e1db0
commit 2af381a
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git 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
@@ -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. 
+