Payout Info on WebUI Dashboard
On the storage node dashboard, you will find the total earnings, total held amount and a detailed payout calculation. On the satellite side, we have to backfill the database first. My expectation is that the storage node will show 0 for now and the held amount in the detailed payout calculation looks incorrect as well. It still contains a lot of useful information that is worth displaying.
Audit Suspension Mode
To avoid unnecessary disqualifications we ignored unknown audit errors for a while. For example a wrong system clock or a disk IO error. With the preflight check, we caught most of the errors. For the remaining errors, we introduce a suspension mode. A storage node in suspension mode will not get selected for uploads and the repair service will repair segments that are in danger. The storage node will still get additional audits even in suspension mode. It should take only a few successful audits to get out of the suspension mode. More information you can find here: Design Draft: Storage Node "Suspended" State Note: Unfortunately the storage node gets no notification about the suspension mode. That part will be finished in 1 or 2 releases. Meanwhile, we will not disqualify storage nodes in suspension mode.
Repair in Memory or on Disk
The old repair worker was consuming a lot of memory. We added a config to switch between repair in memory or on disk. The default is on disk.
Separate Garbage Collection Service
Garbage collection needs a lot of memory as well. We added a config to run garbage collection as a separate process or as part of satellite core. The default is a separate process.
I know everyone would like to see the new payment dashboard but please remember the rollout will take a week. Don’t panic if everyone is talking about the new version but your node is not updated.
It means it can take up to 7 days until the docker image is published and might take 3 more days until your node updates if you’re on docker. Windows nodes will likely update within those 7 days.
But actually it means, don’t worry about being on the latest version on day one. Your node will update when it’s ready.
I confirm it worked. But the “storagenode-updater” windows service did not start automatically after being updated itself. Starting the service manually worked.
This is also my Question. Stopped the Docker manually and pulled… but said its up to date:
docker stop -t 300 storagenode
docker rm storagenode
docker pull storjlabs/storagenode:beta
beta: Pulling from storjlabs/storagenode
Digest: sha256:10d50744ee9262970e5ebfb2d262078f9c691345207e68f4782ebc4c20eaa056
Status: Image is up to date for storjlabs/storagenode:beta
docker.io/storjlabs/storagenode:beta
Thanks
Markus
Ah found something… I think this must be "docker pull storjlabs/storagenode:alpha now?
And also Edit the Docker run Command with “alpha” instead of “beta”?