My nodes received the BF for SLC too, but the date is more recent
2024-07-09T19:15:29Z INFO retain Prepared to run a Retain request. {"Process": "storagenode", "cachePath": "config/retain", "Created Before": "2024-06-30T14:28:54Z", "Filter Size": 6496965, "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
Likely a vice versa, you likely have had WARNs from the collector (it’s a TTL collector), the GC one is called gc-filewalker and retain.
However, since you received a BF for the older date, then perhaps you are correct and TTL collector could be faster.
My nodes have had dozens WARNs related only to the collector, not gc-filewalker or retain. Well, they actually have had a one WARN though too, but not dozens as for collector.
Yes, it’s a known bug and should be fixed in 1.108.x as far as I know,
And I added your comment about piece_expiration.db to the issue