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

[Doc] PQ and DLQ do not support NFS (#14095) (#14100)

Browse source 
* [Doc] PQ and DLQ do not support NFS
Fixed: #12097

Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>
(cherry picked from commit 90e7c8864e)

Co-authored-by: kaisecheng <69120390+kaisecheng@users.noreply.github.com>
This commit is contained in:
github-actions[bot] 2022-05-16 16:17:46 +01:00 • committed by GitHub
parent 81a3489843
commit 2c1771f89f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/static/dead-letter-queues.asciidoc vendored
View file

@ -86,6 +86,8 @@ specify a different path for the files:
path.dead_letter_queue: "path/to/data/dead_letter_queue"
-------------------------------------------------------------------------------
TIP: Use the local filesystem for data integrity and performance. Network File System (NFS) is not supported.
Dead letter queue entries are written to a temporary file, which is then renamed
to a dead letter queue segment file, which is then eligible for ingestion. The rename
happens either when this temporary file is considered 'full', or when a period

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

@ -29,6 +29,7 @@ Persistent queues do not solve these problems:
* A persistent queue does not handle permanent machine failures such as disk corruption, disk failure, and machine loss.
The data persisted to disk is not replicated.
TIP: Use the local filesystem for data integrity and performance. Network File System (NFS) is not supported.
[[configuring-persistent-queues]]
==== Configuring persistent queues
@ -55,12 +56,6 @@ queue will be sized at the value of `queue.max_bytes` specified in
`logstash.yml`.
The default is 1024mb (1gb).
+
Be sure that your disk has sufficient capacity to handle the cumulative total of `queue.max_bytes` across all persistent queues.
The total of `queue.max_bytes` for _all_ queues should be
lower than the capacity of your disk.
We do not check to see if the disk has enough capacity for `queue.max_bytes` for all queues.
The space check at startup only verifies that each queue has sufficient capacity to reach its `queue.max_bytes`.
+
TIP: If you are using persistent queues to protect against data loss, but don't
require much buffering, you can set `queue.max_bytes` to a smaller value.
A smaller value produces smaller queues and improves queue performance.