These are great news. I hope the storagenode code is prepared for that and nodes getting even bigger than todays larges nodes.
Hopefully you are going to assign enough dev resources into it and stop wasting IOPS on the nodes for databases and filewalkers that run over and over where the node would be better off to serve customer files.
If you listen, there are many ideas for areas where to improve the experience:
Is it possible to clean up temp folder automatically like its going to happen with trash folder now (i think data can be deleted even after 1 hour of inactivity on daily/weekly basis)
Something like suggested here:
I would like to see an improvement regarding notification and/or information about events that are relevant to node operators. There are several.
If Storj makes decisions like halting GC, reverting to previous versions, not sending bloomfilters, restoring trash, etc. etc., I would like to know about it.
We had those in the past and if for example GC does not get executed for weeks it creates a totally wrong impression of the network/customer activity and node utilization for the single SNO. An…
Looking more into one of my nodes disqualification I find that information about it can be improved.
In that nodes dashboard, there is not a single notification:
No notifications yet
And the disqualification message lacks useful information:
Your node has been disqualified on 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S. If you have any questions regarding this please check our Node Operators thread on Storj forum.
It shall be improved:
Disqualification should trigger a notific…
Improvements on managing, monitoring and moving nodes might help
Right now the only way to get the nodes to show up in a specific order is by adding them in the order that I want them to show up.
Could the list of nodes be sort-able by name, age, version, disk usage, bandwidth, (etc… ) ?
I had to move nodes. And using Rsync for this is very slow as it is not well suited for millions of tiny files and for some other reasons.
It is not even the time to transfer that makes it so terrible slow it is the time it needs to compare which files to send.
Here is data of 2 nodes for the final run:
Node 1 : Total received 2.85G, took from Thursday to Wednesday = 6 days
Node 2: Total received 343G, took from Wednesday to Sunday the week after = 11 days
The worst thing of all is that for…
2 Likes