High CPU usage by nodes caused by receiving a new bloom filter while still processing the old one

hm, interesting. My nodes didn’t see a high CPU load

CONTAINER ID   NAME           CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O   PIDS
3d20fef76e67   storagenode5   0.05%     88.22MiB / 24.81GiB   0.35%     1.08GB / 11GB     0B / 0B     35
9fb28e5cf48a   storagenode2   3.28%     452.4MiB / 24.81GiB   1.78%     431GB / 102GB     0B / 0B     292

And only one still has a bloom filter in the cache, but only for one satellite.

2024-04-27T09:45:33Z    INFO    lazyfilewalker.gc-filewalker.subprocess gc-filewalker started   {"Process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "bloomFilterSize": 4099953, "Process": "storagenode", "createdBefore": "2024-04-22T17:59:59Z"}
ls X:\storagenode2\retain\


    Directory: X:\storagenode2\retain


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         4/27/2024  12:45 PM        4099953 ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa-1714067999999645000