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

Add at least once delivery to persistent queue docs

Browse source 
Fixes #6761
This commit is contained in:
DeDe Morton 2017-02-27 19:27:49 -08:00
parent 6fb8096a54
commit ebbf36f75f
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -19,10 +19,14 @@ Instead of deploying and managing a message broker, such as Redis, RabbitMQ, or
Apache Kafka, to facilitate a buffered publish-subscriber model, you can enable
persistent queues to buffer events on disk and remove the message broker.
In summary, the two benefits of enabling persistent queues are as follows:
In summary, the benefits of enabling persistent queues are as follows:
* Provides protection from in-flight message loss when the Logstash process is abnormally terminated.
* Absorbs bursts of events without needing an external buffering mechanism like Redis or Apache Kafka.
* Provides an at-least-once message delivery guarantee. 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. In other words, messages stored in the persistent queue may be duplicated, but
not lost.
[[persistent-queues-limitations]]
==== Limitations of Persistent Queues