- Chris Sokolowski
- Site Admin
- Archived posts: 945
- Joined: Aug 27, 2014
May 16, 2017 Mining server status
This morning, our database reached 95% disk usage, primarily consumed by storing old shares. A few weeks ago, we implemented an optimization to reduce the accumulation of new share data and archived some old data. However Postgres’ is designed so that even when you delete data, the disk space consumed by a table is not reclaimed and cannot be reallocated to other tables until we run a full vacuum. I have been putting off this full vacuum since I knew that it would result in delayed shares, but last night, we were finally forced to perform that operation.
At 2:50 AM, I began the full vacuum, and it completed successfully four hours later. The mining server was online the entire time and was accepting shares and finding blocks. However, due to a previously unknown bug caused by the share tables being locked for so long, those shares were not recorded them into the database. Therefore, I have to correct balances. I will be extrapolating the previous hours to get the current earnings. The balance corrections will be applied after the mining server is restarted to resume recording new shares.
I apologize for the issue. As a growing business, we continuously are in a battle to optimize our system to handle ever increasing server load, and as a result, we occasionally have to perform operations we have never done before, like this full vacuum of shares. Now that we know exactly how this operation affects our system, I can assure you that it will not cause issues again.
As always, I will be around to answer any questions you may have. Thank you again for your patronage.
At 2:50 AM, I began the full vacuum, and it completed successfully four hours later. The mining server was online the entire time and was accepting shares and finding blocks. However, due to a previously unknown bug caused by the share tables being locked for so long, those shares were not recorded them into the database. Therefore, I have to correct balances. I will be extrapolating the previous hours to get the current earnings. The balance corrections will be applied after the mining server is restarted to resume recording new shares.
I apologize for the issue. As a growing business, we continuously are in a battle to optimize our system to handle ever increasing server load, and as a result, we occasionally have to perform operations we have never done before, like this full vacuum of shares. Now that we know exactly how this operation affects our system, I can assure you that it will not cause issues again.
As always, I will be around to answer any questions you may have. Thank you again for your patronage.
Last edited Tue May 16, 2017 08:46 PM UTC by Chris Sokolowski; edited 1 time(s).
