Existing problems at the moment

[jammerdan]

@Alexey

Perhaps I missed them and have only threads where you are posted your issues so far.

Here are some:

Current situation with garbage collection

Am I the only one seeing trash folders like this? Doesn’t really make sense to me: ./pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa/2024-04-13/2024-04-13/2024-04-12/36

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

Ubuntu, Docker, 1.101.3 Scenario: The node receives a bloom filter from the US satellite and starts the gc-filewalker. 2024-04-22T03:18:05Z INFO retain Prepared to run a Retain request. {"Process": "storagenode", "cachePath": "config/retain", "Created Before": "2024-04-10T17:59:59Z", "Filter Size": 1351678, "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYLZHeLUtdps3S"} 2024-04-22T03:18:05Z INFO lazyfilewalker.gc-filewalker starting subprocess {"Process": "storagenode", "sate…

Bloom filter (strange behavior)

I noticed strange behavior with the bloom filter file ON THE WINDOWS 10! When a node receives a bloom filter, it saves it to disk in the /retain folder as a file with the name of the satellite (ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa-1714067999999645000). Next, the work of collecting garbage begins. A folder with the name of the current date appears in /trash and garbage collection begins there. BUT! If during garbage collection the node is restarted for some reason, the bloom …

Trash does not go away in 7 days

hello. Last week they deleted a lot, it has been 7 days but they have not freed up the space. Has anyone else noticed?

Another issue with trash

I’m gonna have to agree with this @clement . If the downgrades are indeed what caused this, it can’t be up to SNOs to fix this. And it really sucks that despite warnings from us (including me) about the wrong minimum version on versions.storj.io, very early in that upgrade cycle, you did nothing to prevent those downgrades. And in fact, the same issue happened again on the next rollout. Which btw, if it happens when rolling out 1.105, downgrading nodes from 1.104 will instantly break them due t…