-
Notifications
You must be signed in to change notification settings - Fork 184
Description
Search before creating an issue
- I have searched existing issues and confirmed this is not a duplicate
Bug Description
Based on #8453.
The proxy cache doesn't help with the above situation because the proxy is different each time, it misses the cache and just gets added as a new entry. I think the proxy cache has a few other problems: I can't see any call to purgeExpired, so I don't think old proxies will ever be tidied up unless explicitly asked for and expired? The lifetime of the SiteDirector process is maybe a few hours (when it reaches its MaxCycles and restarts) but the proxy lifetime is days, so the cache dictionary gets "lost" during the restart and it never gets to the point of deleting the expired proxies anyway.
Maybe add some kind of destructor/shutdown call to ProxyManagerClient's cache so that it deletes proxies when the cache is destroyed (or ideally don't rely on that behaviour in the first place and tidy old proxy files up as soon as they're no longer needed although knowing when that is seems more complicated).
If #8453 is not sufficient, we should try to investigate DictCache cleaning process and see if there is any issue.
- Explore DictCache cleaning mechanism
- If any issue, add reproducing tests
Steps to Reproduce
No response
Expected Behavior
No response
Actual Behavior
No response
Environment
No response
Relevant Log Output
Additional Context
No response