Will Fluent bit truncate the log? #7502
liguangcheng
started this conversation in
General
Replies: 1 comment
-
root cause is clear: fluent uses inode to compare the old and new file in DB, if new file use the same inode with old`s, then the offset of old file will be assigned to the new file, finally the new file content will be read from the offset instead of 0 |
Beta Was this translation helpful? Give feedback.
0 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.
-
I used Fluent Bit v2.0.8 in production environment, recently I found a strange phenomenon that fluent bit truncate the log.
I have a lot of files that all content are xml format, when I used the Fluent-bit to transfer these contents to Splunk server, some of these files will be truncated, there are some files where only part of a certain line is transferred, that is to say, a certain line is truncated.
I also have some files that content are json format, but I did not observe truncation, that means I only observer that xml format content truncated.
Has anyone encountered this problem?
Beta Was this translation helpful? Give feedback.
All reactions