In the past few days I have tested garbage collection to make sure it deletes only garbage and nothing else. If you want to know more about garbage collection you should take a look at https://github.com/storj/storj/blob/538e8168a524a82ef63c6afd2b6d93bb044dca81/docs/design/garbage-collection.md
The next step is to enable it on one or two satellites to catch possible performance impacts and to double check which pieces it would delete.
Please help us to verify that the garbage collection works as expected.
What do you need?
- A big logfile that includes a few weeks of lifetime.
storage2.retain-status: "debug"to your config file and set
log.level: debugas well. Debug mode means the storage node will execute garbage collection without deleting anything. It will only create logmessage with the pieceIDs it identified as garbage. Please use only debug mode for now!
- Restart your storage node and wait until the satellite sends you a garbage collection message. I will let you know when this should happen.
- At some point you will see
About to delete piece idor
Deleted 0 pieces during retainin your logfile. Do you get any of these messages?
- Copy the pieceIDs and search for it in the logfile. A regular expression like
grep 'ID1\|ID2\|ID3'is usefull here. We don’t want to see any audit requests for pieceIDs after the garbage collection message.
I don’t expect any performance impact in round 1 because we are starting with a smaller statellite.