From b238d9483dafd3617101714c7f591930f94af345 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz?= Date: Tue, 14 Feb 2017 15:26:27 +0100 Subject: [PATCH] single typo fixed Fixes #6702 --- docs/static/persistent-queues.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/static/persistent-queues.asciidoc b/docs/static/persistent-queues.asciidoc index cf0113b1e..547ba8945 100644 --- a/docs/static/persistent-queues.asciidoc +++ b/docs/static/persistent-queues.asciidoc @@ -143,7 +143,7 @@ When recording a checkpoint, Logstash will: The following settings are available to let you tune durability: * `queue.checkpoint.writes`: Logstash will checkpoint after this many writes into the queue. Currently, one event counts as one write, but this may change in future releases. -* `queue.checkpoint.acks`: Logstah will checkpoint after this many events are acknowledged. This configuration controls the durability at the processing (filter + output) +* `queue.checkpoint.acks`: Logstash will checkpoint after this many events are acknowledged. This configuration controls the durability at the processing (filter + output) part of Logstash. Disk writes have a resource cost. Tuning the above values higher or lower will trade durability for performance. For instance, if you want to the strongest durability for all input events, you can set `queue.checkpoint.writes: 1`.