High CPU usage by node caused by receiving a new bloom filter while still processing the old one. Also new gc won't start after processing old bloom filter about storj HOT 7 OPEN

Do I understand correctly that if a node receives more than one bloom filter from a single satellite, it tries to process all of them at the same time?

Yes. Setting --retain.concurrency to 1 should switch processing to do filters one by one. It might be less optimal when receiving two or more filters from different satellites but usually satellites other than US1 are processed much faster.

Before doing something more elegant we plan to set default value --retain.concurrency to 1 to mitigate this issue on larger nodes.

from storj.

Thank you for your report. We are looking into this issue. As temporary workaround you can try reducing --retain.concurrency from default 5 to something lower to reduce CPU load.

from storj.

Change storagenode/retain: reduce concurrent retain requests to 1 mentions this issue.

from storj.

As temporary workaround you can try reducing --retain.concurrency from default 5 to something lower to reduce CPU load.

Do I understand correctly that if a node receives more than one bloom filter from a single satellite, it tries to process all of them at the same time? It is unclear because in the log, i see only the first one being processed. For now, it is not a problem when the node processes two or more blooms from different satellites concurrently; it does not cause high CPU load. The problem appears only when the node has multiple retain requests from a single satellite.

from storj.

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/high-cpu-usage-by-nodes-caused-by-receiving-a-new-bloom-filter-while-still-processing-the-old-one/26007/13

from storj.

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/gc-successfull-bloomfilter-not-deleted-new-bloomfilter-not-processed/26194/8

from storj.

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/gc-successful-bloomfilter-not-deleted-new-bloomfilter-not-processed/26194/13

from storj.