Move Kademlia Hash table file to memory or system drive instead of storing on node drive due to constant file access and small file size
Apr 5 2019
Enter a subject
Ryan Curtis commented
24 Apr 02:36
If file is stored in memory, there is risk of losing the hash table on every break in node uptime. This could be negated by flushing back to disk when safely stopping the node. Since the file size is very small, this would be my choice. The risk then would just be if the node crashes unexpectedly. Then you may have to rebuild the hash table from scratch. Perhaps checkpoints every 6 hours to disk or so could be used to defer this risk.
Open full size
Log in / Sign up
Identify yourself with your email address
You won't be notified about changes to this idea.
Hash SNO errors. If the hash is unique, send the error to storj. Storj stores hash. Future SNOs check storj to see if it is known issue and whether SNO should be concerned about said issue
Option to make files public access and to set a fee for downloading where those funds go to the network to cover bandwidth and hosting.
If every one could storj storage node's reputation easily. Then the nodes' quality could be impoved precisely.
Email notification in case the node goes OFFLINE
Remote api monitoring of node statistics and status
Use more threads when generating keys for a new node.
Multi-HD setup for a single node
Allow for a storage node to perform planned maintenance
Storage node with proxy ( i.e. without portforwding need)
Green light on Dashboard if the node is working as intended, Red light when abnormal.