Alexey
June 26, 2020, 8:11am
4
Sorry for inconvenience!
I created an internal issue for this bug.
The reason is simple - we have had paused the rollout because of the bug: Fatal message on SN and all docker versions are stuck in 1.5.2, part of Windows versions are on 1.6.3, because they updates first:
Yes, it’s because Storj uses a phased rollout to make sure new updates aren’t causing a problem and take down all nodes at once.
[image]
The timelines are an indication, it doesn’t always take exactly 7 days before the docker version is available, but it follow this pattern.
Now we started a rollout of the new version:
For Storage Nodes
In Memory Used Serials
The storage node keeps the used serials list in memory instead of writing them into a SQLite DB. Serial numbers are used for double spend protection. To minimize memory usage we decreased the expire time for uplinks from 24 hours to 1 hour. Within 1 hour the uplink needs to start the transfer because otherwise, the storage nodes will reject the order. The transfer itself can still take longer than 1 hour. Orders are also still valid for 48 hours. Afte…
1 Like