Well, the initial onslaught has been quieted. It wasn't a pretty transition as far as transitions go, but it could have been much worse.
We are now running a beefy set of four servers (thanks in large part to Sifter contributions) consisting of a load balancer front-end, two web servers, and a DB server.
There were several challenges we had to overcome to get this all worked out properly, but everything is now running at full speed and our load is lower on both web servers than it's been for a long, long time.
There may still be an issue here or there, but everything seems to be working surprisingly well at the moment. (Yay!) Knock on wood.
We are now running a beefy set of four servers (thanks in large part to Sifter contributions) consisting of a load balancer front-end, two web servers, and a DB server.
There were several challenges we had to overcome to get this all worked out properly, but everything is now running at full speed and our load is lower on both web servers than it's been for a long, long time.
There may still be an issue here or there, but everything seems to be working surprisingly well at the moment. (Yay!) Knock on wood.
Stumble This
*knock, knock, knock*
The Sift has more power! Yay!
Well done!
It's a bit early to be sure, but i've noticed a tendency to get logged out a bit more often than I remember. I'll continue to watch for it to be sure.
lol
Yeah, I've been frequently logged out (but only on this computer at work and not at home for some reason). I'll see if I can figure out exactly what's causing it and try to make it stop.
The technical explanation is that requests from the same login are supposed to repeatedly go to the same back-end server, but for some reason the load balancer that decides which one to send you to is not doing a proper job of it. So it sends you to the other server after a while, and you have to log back in on that one. (Annoying, I know.)