Discovery Throttle

Explanation

Discovery for all scans has been temporarily paused due to a high volume of pending files in the queue. This proactive measure is in place to optimize system resources and prevent excessive RAM consumption. By implementing this limit, we ensure efficient processing and mitigate the risk of the queue becoming infinite. This occurs when the rate of discovery outpaces the scanning capacity.

The maximum pending files value is given by the .env variable DISCOVERY_THROTTLER_MAX_PENDING_FILES which has the default value 5000.

Solutions

Should this persist as an issue, consider adjusting the DISCOVERY_THROTTLER_MAX_PENDING_FILES to accommodate more pending files, albeit at the potential expense of RAM. Additionally, upgrading your system specifications could offer a sustainable solution to mitigate such bottlenecks.