You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These segments each contain 3 log messages that were rejected by Elasticsearch with a 400 mapping issues, they were correctly pseed to the DLQ, edited by a filter and re-processed, and I can see them now in the intended index. But these used segments have not been cleaned from disk, which is the intended use of clean_consumed.
It says that when clean_consumed is set to true, then commit_offsets must also be set to true, which I've done. It also states that sincedb tracks the checkpoint of the DLQ, but I cannot find any trace of it writing any checkpointing files in <path.data>/plugins/inputs/dead_letter_queue:
The DQL is functioning correctly but without cleaning up the used log segments it is not fit for purpose to be released into my Production environment. The documentation here:
Logstash information:
Please include the following information:
logstash 8.7.0
systemd
logstash-input-dead_letter_queue **(2.0.0)**
JVM (e.g.
java -version
):OS version (
uname -a
if on a Unix-like system):20.04.1-Ubuntu
Description of the problem including expected versus actual behavior:
clean_consumed
option does not clear used segments as per documentation.These segments each contain 3 log messages that were rejected by Elasticsearch with a 400 mapping issues, they were correctly pseed to the DLQ, edited by a filter and re-processed, and I can see them now in the intended index. But these used segments have not been cleaned from disk, which is the intended use of
clean_consumed
.Steps to reproduce:
logstash.yml DLQ settings:
pipelines.yml file:
DLQ input file:
Looking at the documentation here:
https://www.elastic.co/guide/en/logstash/current/plugins-inputs-dead_letter_queue.html
It says that when
clean_consumed
is set to true, thencommit_offsets
must also be set to true, which I've done. It also states thatsincedb
tracks the checkpoint of the DLQ, but I cannot find any trace of it writing any checkpointing files in<path.data>/plugins/inputs/dead_letter_queue
:The DQL is functioning correctly but without cleaning up the used log segments it is not fit for purpose to be released into my Production environment. The documentation here:
https://www.elastic.co/guide/en/logstash/current/dead-letter-queues.html#auto-clean
Does suggest maybe there's a formatting issue, but not sure whether that's an error in the docs.
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: