I'm rearranging the server layout.
Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.
It's a new front end server for the pool and will simplify the next change.
That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.
If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)
Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it
The process is progressing well.
A few minor issues with the old backend provider, supplying a problematic server for a frontend, so I wont be using them for that ever again (i.e. none of the new servers are from them)
As I've already mentioned, I've pointed the DNS to a new frontend for mining.
When I change the backend over to the new one in the next 24-36 hours, I'll simply modify where it sends/gets it's work so, of course, no one will need to change anything when I do that, but as mentioned above, there will be about a 5 minute mining outage when that happens.
I'm also setting up (almost done) a new front end server to the web site - the 2nd new server mentioned above.
That will be done before the final change over.
It will also be able to be easily switched from getting data from the old server to the new server when the change over occurs.
Web/API access will probably be a longer outage when the changeover occurs, since there's 2 steps, the back end move, and then a ckdb restart (or 2) which adds another 5-10 minutes to the outage.
i.e. it could be up to a 15 minute web/api outage when I do the final change.