Our master database has been getting closer and closer to its limit over the past month, and instead of waiting for it to die fully, I've got a new one spooled up and ready to go. Its about 4x as big (in terms of performance), so we should have a large amount of head-room for the future. Ideally we'll be moving over to the new server tomorrow afternoon if everything in our tests goes correctly.
This shouldn't affect any miners, but will possibly affect anyone pulling stats from our API during the cut-over time. Shares from endpoints are logged to a share-collector before being processed into the DB, and that share collector will be unaffected. Most likely you'll see stats stop updating (if you're looking at a 3rd party stats site), or you'll see our webpage go down with a "Maintenance" banner.
Once we swap over to the new database completely, all of the pending shares will be processed, so you might see a drop in hashrate, and then a huge spike in hashrate, this is expected just because of the delay in processing shares.
We don't expect the cut-over to take more than 15-30 minutes, but it could possibly take up to an hour.
If anything were to happen that would cause a loss of shares from stratum endpoints (not planned), I will shut off the stratum endpoints entirely, and your miner will failover to a backup pool until we're back up and running. You have a backup pool configured, correct?
I have to say, you are by far one of the best pool operators when it comes to communication. In a crypto-world where everyone loves to yell 'scam!' at the first sign of trouble, it is good to get a clear and concise heads up when things will be slightly out of the ordinary for a small amount of time.
Keep up the good work!