timeoutRate never decreases
sibblegp opened this issue · 1 comments
Package Versions
Replace the values below using the output from storjshare --version
.
daemon: 5.1.0, core: 8.2.1, protocol: 1.2.0
Replace the values below using the output from node --version
.
v6.11.4
Expected Behavior
As time passes, timeoutRate should decrease and eventually get back to zero. This should probably start happening after a set time after the last timeout and over a period of time after that.
Actual Behavior
As it stands, it never decreases. This means as small as a ten minute interruption or even restarting the daemon can cause a node to get a timeoutRate no matter how much uptime it has previously which will severely hamper its operation. How are we supposed to maintain machines (adding hard drives, RAM, dealing with filled memory because of memory leaks in the daemon) when a timeout basically kills a node? Considering these are not servers running 99.999% uptime, some downtime is to be expected and some forgiveness for it (especially over time) should be part of the equation.
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
- Have a node with 100% uptime for weeks/months.
- Stop the node for 30 minutes.
- The node will probably have a timeoutRate now.
- Sharing and mirroring to the node will dramatically decrease permanently.
- The timeoutRate will never decrease and the node is essentially useless to you as a farmer despite working perfectly except for a minor interruption.
Copy of storj-archived/complex#81