Filebeat Still holding the log files even after i upgrade from 5.1.2 to 5.5.2

Filebeat still holding the log files and not closing it after the logs are rolled out. Which creates the space issue. Previously we had 5.1.2 which had this issue and after we upgrade we thought the issue will be gone but it did not. Once we kill the service the space utilization is greatly reduced.

Are you using the close_inactive / clean_inactive flags? Can you share your filebeat.yml configuration?

Hi Adrisr,

I have changed the close_inactive=5 min. let me see if that fixes the issue. Otherwise i will share the yml file. Thanks for your reply.

Naganathan V

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.