You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
by design, lumberjack sometimes holds onto file handles of deleted files. This is so that we can continue shipping lines from a given file even after it has been deleted, if we haven't already shipped all of the lines.
also by design: if all logstash connections are down, lumberjack will automatically wait for them to come back online before continuing.
this means that if logstash has failed completely, and lumberjack can't ship anything, it'll just open file handles on log files as they are created, and never let go of them, potentially filling disks. The alternative of letting go of the file lets the OS reclaim its disk space, but at the cost of not shipping those lines. That appears to be an acceptable tradeoff.
The text was updated successfully, but these errors were encountered:
by design, lumberjack sometimes holds onto file handles of deleted files. This is so that we can continue shipping lines from a given file even after it has been deleted, if we haven't already shipped all of the lines.
also by design: if all logstash connections are down, lumberjack will automatically wait for them to come back online before continuing.
this means that if logstash has failed completely, and lumberjack can't ship anything, it'll just open file handles on log files as they are created, and never let go of them, potentially filling disks. The alternative of letting go of the file lets the OS reclaim its disk space, but at the cost of not shipping those lines. That appears to be an acceptable tradeoff.
The text was updated successfully, but these errors were encountered: