Changelog v1.10.1

For Storage Nodes

Copy Satellite ID
The storage node dashboard and the payment dashboard contain a drop-down list with all satellites. On the dashboard, we show the satellite names but in the logfile and other places we print out the satellite ID. The drop-down list has now a toggle to switch between satellite name and ID including a copy button for the satellite ID.

Garbage Collection Logging
Garbage collection will move data into a trash folder and delete it after 7 days. These 7 days are an insurance against possible bugs around garbage collection. It is possible that the satellite sends out empty bloom filters which would wipe out all data. Within 7 days the satellite can send a restore command to all storage nodes.
The logging around garbage collection is now fixed. First the storage node will write About to move piece to trash and Moved pieces to trash during retain . 7 days later deleted piece . All 3 messages on log-level debug.

For Customers

User Value Attribution
For open-source projects, we offer an open source partner program . In addition to bucket value attribution, we have now implemented user value attribution. Open source projects can link our signup page with a partner ID. User value attribution has a higher priority over bucket value attribution. If the user has a partner ID we will use that for all buckets no matter which application will be used for creating the bucket. If a user has no partner ID we fall back to the partner ID provided by the application on bucket creation. Later we will calculate a payout for each partner ID. We want to support open source projects by sharing profit with them.


So now it will really MOVE (like mv) or it will be copied to trash folder (like cp)?

Yeah, the cp old new;rm old method is a bit annoying.

1 Like

Only the logging was changed.

Less safe too. Additional roundtrip through (usually) non-ECC memory.

plus more iops on the HDDs, I really do not get why trash is copied instead of moved

Irrelevant, nearly all of these pieces are to be deleted, but reed solomon protects them anyway. They live on hard drives anyway, which are prone to failure and bit rot.