Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dcache-qos: remove trigger to rescan pools on tag change
Motivation: Resilience had its own internal representation of the Pool Selection Unit which it maintained in a centralized location accessed by both the update operations as well as the pool scan operations. In migrating this functionality to QoS, it was decided, for a number of reasons, that this was no longer desirable or necessary, and that instead accssing the PSU shipped along with the Remote Pool Monitor was sufficient. An unanticipated consequence of this decision, however, now manifests itself in the way every restart of a pool, and all pools on initial startup, trigger forced scans. The reason for this is that the sequence of diff's between the current PSU and the new one will not always provide the pool tags (in the cost module) immediately, so it always looks like (to QoS) that they have changed. This can even happen periodically if the pool monitor does not carry the tags (= null) and then on the next iteration it does (periodic rescans can now be observed). One solution might be to rectify the diff logic, but this would require maintaining, once again, an ad hoc data structure based on the PSU along with the PSU. However, the problem which is trying to be handled here itself needs re-evaluation. The original idea was that if the pool tags change, files which are distributed across pools based on these tags may need redistribution. But, unlike changing the requirements for the storage unit, changing the actual pool tags requires a pool restart. I do not think it unreasonable in that case to require that the admin responsible for changing those tags also decide whether the files involving those pools will require immediate redistribution, and if so, simply forcing a scan of the pool manually via the admin command. Hence the simplest solution is to eliminate the attempt to discover this and automatically force the scan. In the event the admin does not schedule the pool for scan, the consequences of the changed tags will nevertheless be immediately felt for new files, and the redistribution will eventually take place during periodic scans. Modification: Remove the scan trigger code for changed tags. Result: No more scannning of all pools at startup or periodic rescanning of all pools outside the periodic window. Target: master Request: 9.1 Request: 9.0 Request: 8.2 Patch: https://rb.dcache.org/r/14009/ Requires-book: yes (included) Requires-notes: yes Acked-by: Tigran
- Loading branch information