mirror of
https://github.com/elastic/logstash.git
synced 2025-04-25 07:07:54 -04:00
parent
b709eb5c68
commit
31b2a36346
1 changed files with 4 additions and 1 deletions
5
docs/static/persistent-queues.asciidoc
vendored
5
docs/static/persistent-queues.asciidoc
vendored
|
@ -25,6 +25,9 @@ Redis or Apache Kafka.
|
||||||
a normal shutdown as well as when Logstash is terminated abnormally. If Logstash
|
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
|
is restarted while events are in-flight, Logstash will attempt to deliver
|
||||||
messages stored in the persistent queue until delivery succeeds at least once.
|
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]]
|
[[persistent-queues-limitations]]
|
||||||
==== Limitations of Persistent Queues
|
==== 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)
|
* `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.
|
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.
|
The process of checkpointing is atomic, which means any update to the file is saved if successful.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue