Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.8.0
-
None
-
None
Description
Current behavior of Taildir is such that if a file is renamed (eg log rotated) it is consumed again.
Would not be better if the inode is followed, and if that inode has been consumed do not consume it again? With current implementation, once file is rotated, you get duplicates in the case you include in the path previous days's data (you want to do that if agent fails and needs to consume data from previous days).
Attachments
Issue Links
- Blocked
-
FLUME-3341 Taildir source may cause file handle leak and data duplication
- Patch Available