Release tonight

News updates about the Prohashing pool
Forum rules
The News forum is only for updates about the Prohashing pool.

Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Release tonight

Post by Steve Sokolowski » Wed Oct 06, 2021 1:52 pm

At around 8:30pm or 9:00pm EDT, we'll be issuing a release. We expect a 1s interruption of connectivity for mining, but it could take longer if things don't work as they did in testing.

The purpose of this release is to dramatically simplify how the share inserters communicate with the mining servers, to make them far less likely to miss any shares, and to significantly reduce memory usage in the share inserters. The changes aren't needed unless the database gets behind, and we want this redundancy to be available tonight when Chris fixes the issues that caused the database to get behind in the first place.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Release tonight

Post by Steve Sokolowski » Thu Oct 07, 2021 6:53 am

This release has been completed. In this release, we:
  • Updated the mining servers and share inserters to dramatically refactor their connections to a much simpler way to send shares to the inserters, which will remove the need to queue the same shares in both components and be more reliable in catching up when an error occurs elsewhere in the system
  • Updated the Chia mining server to comply with the new share inserter functions
  • Updated the Coinbase payouts program to not hold transactions open while sending money; instead, it will insert a payout row, commit it as if the money was sent, attempt to send the money, and then either do nothing on success or delete the row on failure. This change will prevent the system from falling behind due to payouts holding open locks
  • Replaced a faIled memory module in the database server, restoring it from 192 to 256GB of working memory
  • Rebooted the ETH daemon server, to apply critical operating system security patches announced by Debian linux
  • Deleted the corrupted indexes created in May from the database upgrade while there were no locks on the tables
  • Added pagination to the website for miners and other live data, which will significantly improve dashboard load time for large customers
  • Added an additional check to the auditing system to warn when one algorithm is responsible for more than 10x the value of shares/money than the next closest algorithm is
Locked