Replies: 1 comment 3 replies
-
For clarity, are you seeing that vector re-reads logs messages that were already handled before the restart, or that it continues reading log files that it had open after the restart? If it is the former, it is a bug, as that should automatically be handled by the checkpoint logic. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
As per vector docs for ignore_older_secs Vector should ignore files with a modification date older than the specified time.
But when we restart the vector application we see that vector starts processing the same logs that were already processed before the restart. After some research we found out that during vector restart it using the ignore_older_secs to determine where to resume from.
The calculate ignore before and the set state for the checkpointer seems to clearly indicate our findings. The ignore_older_secs is being used by the checkpoints.
Please can we get some some clarifications on exactly how to use ignore_older_secs. Our main problem here is that when we restart vector, we want to resume processing from where vector last left off. I am not finding anything specific about the checkpoints in this discussion thread
Beta Was this translation helpful? Give feedback.
All reactions