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

Add note to clarify at-least-one guarantee statement

Browse source 
Fixes #7029
This commit is contained in:
DeDe Morton 2017-05-04 13:00:40 -07:00
parent b709eb5c68
commit 31b2a36346
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/static/persistent-queues.asciidoc vendored
View file

@ -25,6 +25,9 @@ Redis or Apache Kafka.
a normal shutdown as well as when Logstash is terminated abnormally. If Logstash
is restarted while events are in-flight, Logstash will attempt to deliver
messages stored in the persistent queue until delivery succeeds at least once.
+
NOTE: You must set `queue.checkpoint.writes: 1` explicitly to guarantee
maximum durability for all input events. See <<durability-persistent-queues>>.
[[persistent-queues-limitations]]
==== Limitations of Persistent Queues
@ -148,7 +151,7 @@ The following settings are available to let you tune durability:
* `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`.
Disk writes have a resource cost. Tuning the above values higher or lower will trade durability for performance. For instance, if you want the strongest durability for all input events, you can set `queue.checkpoint.writes: 1`.
The process of checkpointing is atomic, which means any update to the file is saved if successful.