Help us to test garbage collection

Product Discussions STORJLINGS
21

Looks good! Anything else you want us to look for on our nodes?

Will enabling garbage collection (after the update) require a change in the config for:

  • Those who have tested in debug (us)?
  • Other users?
22

I enabled debug mode on both my AcePC and Raspberry Pi nodes.

23

No. For the moment you can keep it as it is. With the next release it will be enabled on all satellites but not on the storage nodes. I donā€™t want to risk that. We better watch it a few more days.

24

Do not activate it! You can get disqualified

I was able to break garbage collection. An uplink has to upload the pieces to the storage nodes within 1h otherwise the storage node will not accept it. After that the uplink has plenty of time to report back to the satellite. Lets say the uplink is just waiting 90 minutes for some reasons. The storage node has a buffer of only 60 minutes and will delete the new pieces before the satellite knows about them.

Issue created and now we have to wait for a fix.

25

Anyone who participated in this test, please be aware that the debug setting causes v0.19.0 to fail. You should remove the storage2.retain-status: "debug" line from your config.yaml

If you already ran into this issue and your node isnā€™t starting:

  • Stop the node
  • rm the container
  • remove the line from the config.yaml
  • run your node with the run command
26

How did it fail for you? My node looks good after the update.

27

I got the following error.

2019-08-27T21:35:35.442Z        INFO    Configuration loaded from: /app/config/config.yaml
2019-08-27T21:35:35.442Z        INFO    Invalid configuration file key: storage2.retain-status

And then a repeating looping of

2019-08-27T21:35:35.442Z        DEBUG   debug server listening on [::]:7777
2019-08-27T21:35:35.452Z        WARN    Operator email address isn't specified.
2019-08-27T21:35:35.452Z        ERROR   Invalid configuration: operator wallet address isn't specified
2019-08-27T21:35:35.452Z        FATAL   Unrecoverable error     {"error": "operator wallet address isn't specified"}

Though now Iā€™m starting to think it may have also been a watchtower related glitch that made it somehow lose the run arguments.

28

I also got the invalid configuration file key information after update. Iā€™ve removed the invalid configuration file key.