I'll bake you a cupcake so sweet...4.05 / 5.00 16,479 Views
Aliens, evil wizards, space vampires, & Shyfters! Just another day in the life of a badass3.89 / 5.00 7,366 Views
Stop the killer bees3.83 / 5.00 3,473 Views
I've noticed a bug. My inbox says I have one unread message, but there's nothing new there when I look.
9/11 never happened. Don't believe the lies.
At 7/31/12 05:31 PM, Chdonga wrote: I've noticed a bug. My inbox says I have one unread message, but there's nothing new there when I look.
That's been around for a while. I've never experienced it myself, but I think the solution is to send or receive a message. As it's an inbox, my money's on receive.
Everything works fine on the site, except the front page.
I still get the message that the site is being maintained, or that's just me?
At 7/31/12 11:37 AM, MikeyS9607 wrote: I don't understand from a programming point of view, like when you use an insert query in MySQL, does the server not pick it up till later?
They're using a cluster of servers for their database, several of them are read-only to speed up random views on "static" content. Normally changes made are replicated immediately however a fault has caused them to lag behind a bit.
Basically the way it works is we have a master database server and a batch of slave servers. The idea is on pages where you only need to read data (especially slower lookups like keyword searches), we use the slave server. These servers are load balanced so if one is busy, it uses a different one, thus keeping page loads nice and efficient.
When we need to add any information, like posting a message, or submitting content, it writes to the primary database. We never directly write data to the slave servers, rather, they use a sort of query queue. When the master database gets a new item added, it adds that query to the slave queue and those all get run in order.
The problems we have been experiencing come from an issue where this queue on the slave servers is falling radically far behind the master. Typically they run immediately, but some of our big automated jobs take a little longer and the slaves fall behind. The site still runs fact because everything is doing what it's supposed to, but new data (such as a newly submitted movie) doesn't exist on the slave server yet, so the submission page throws an error. After a few minutes, the slave catches up and the submission magically works.
Anyway, this latency was something that obviously should not have been happening, so that's why we had the downtime yesterday.
Arch-Angel likes this sig!
At 8/2/12 02:10 PM, PsychoGoldfish wrote: Anyway, this latency was something that obviously should not have been happening, so that's why we had the downtime yesterday.
so the big problem was a few larger things getting moved into the slaves?
hm. What was the fix, simply not allowing people to do anything until the servers caught up, or did you wait and then reboot the machines the DBs were on?
At 8/3/12 12:03 PM, Ectohelix wrote: Crud, I was hoping it was maintenance so projects (I've made a couple I'd like to remove) could be deleted. Ah well...
Well, there was another update recently, so that might count as maintenance.
You know the world's gone crazy when the best rapper's a white guy and the best golfer's a black guy - Chris Rock