This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Too many open file handlers Inode reuse causes Filebeat to skip lines »
Elastic Docs ›Filebeat Reference [master] ›Troubleshoot ›Common problems

Registry file is too large

edit

Registry file is too large

edit

Filebeat keeps the state of each file and persists the state to disk in the registry file. The file state is used to continue file reading at a previous position when Filebeat is restarted. If a large number of new files are produced every day, the registry file might grow to be too large. To reduce the size of the registry file, there are two configuration options available: clean_removed and clean_inactive.

For old files that you no longer touch and are ignored (see ignore_older), we recommended that you use clean_inactive. If old files get removed from disk, then use the clean_removed option.

« Too many open file handlers Inode reuse causes Filebeat to skip lines »