Announcement: major storage node release (potential config changes needed!)

[jammerdan]

@pdeline06

This is bad.

Correct.
I have turned filewalker off on several nodes because of that.

I don’t know what is halting the completion of the feature and deploy it. I have asked to get this done several times:

Updates on Test Data

Good. SNOs are used to pain. How much space do you need? Speaking for myself I can add space. I am sure other can too. Please solve this: https://review.dev.storj.io/c/storj/storj/+/12806 I have turned off used space calculation on several nodes so they are reporting garbage. We are getting used to get stabbed in the back.

It seems that the new feature “save-state-resume GC filewalker” isn’t functioning as expected

Not good. That feature is really needed to help when a used space filewalker does not finish for whatever reason.

Database locking madness

Iterating of every file not just once in a while but frequently, maybe that was an idea easy and cheap to implement when nodes were at 500GB. But now with nodes at 15TB this is pure madness. And on top the frequent restarts after updates and everything starts all over from the start except when data was kept in RAM only like with the Bloomfilter until recently fixed. Plus independent from the load aka customer usage of the node it gets hammered by filewalkers, database accesses and all. And …