The current SP code in the file DiscoveryFeed.cpp includes this comment:
// Remove any files unused for more than a couple of minutes. // Anything left will be orphaned, but that shouldn't happen too often.
We are finding with our 2.6.0 deployments (both CentOS 7 and Debian 8) that enough of the cache files are orphaned each day to be a nuisance. The number of orphans appears to be correlated with the load on the system. The busiest service accumulates about 10 orphan files a day. Each one is 1.5 MB in size (due to eduGAIN, these are widely federated SPs), so about 15 MB of orphaned files a day.
We are requesting an enhancement that would reap the orphan files more robustly.
A simple cron job to remove them nightly solves the issue so this is not a high priority, but it is a nuisance for an otherwise "well behaved" system.
The current SP code in the file DiscoveryFeed.cpp includes this comment:
// Remove any files unused for more than a couple of minutes.
// Anything left will be orphaned, but that shouldn't happen too often.
We are finding with our 2.6.0 deployments (both CentOS 7 and Debian 8) that enough of the cache files are orphaned each day to be a nuisance. The number of orphans appears to be correlated with the load on the system. The busiest service accumulates about 10 orphan files a day. Each one is 1.5 MB in size (due to eduGAIN, these are widely federated SPs), so about 15 MB of orphaned files a day.
We are requesting an enhancement that would reap the orphan files more robustly.
A simple cron job to remove them nightly solves the issue so this is not a high priority, but it is a nuisance for an otherwise "well behaved" system.