@#$$%@!!!

[swestrup]

The dang livejournal system kept saying it had taken my journal entry, but wouldn't show it, even after I re-entered it. When I asked to edit the last entry submitted, it showed the entry before. Okay, maybe its my machine. So I reboot, log back on, re-enter the text, and resubmit it. No dice. Try again. NOW there are FOUR copies of the damn thing! Okay, no problem, I'll just erase three of them. Ask to edit the last entry. Nope, its never seen any of the four copies. So, I'm just going to go to bed now, and I assume, whatever the dang system says, that this message will eventually show up explaining what happened.

Comments

So Stephen's theory is

[sps.livejournal.com]

that there are about a dozen servers arranged pretty much they way we were planning at SG. Theoretically they should be in approximate synch, but at the moment as soon as the load goes up propagation starts taking on the order of 20 minutes. As far as I can tell, so long as you get a confirmation it was really logged; if you get an 'empty page' return, there really was a load failure and you really do need to resubmit.

[denizsarikaya.livejournal.com]

Yeah, what SPS said.

Also, if you're not a paid member, it's nearly guaranteed it'll take a while before you'll see the updates. There's a hierarchy in speed on servers, with paid members getting access to faster ones.

[sps.livejournal.com]

I hope it wasn't engineered incompetently in order to get people to pay...! I can't honestly see a need for delays more than about three times the diameter of the internet plus a second or so, even with randomly placed replicas, unless you're trying to do something secure (as in: against major governments).

But probably this thing is based on "standard" (i.e. wildly inefficient and grossly unsuitable) technology.

-grumpy me

this is unusual

[denizsarikaya.livejournal.com]

Erm, this week has been pretty bad. And tonight is the worst I've seen barring when LJ was attacked pretty effectively two months ago.

If you check out http://status.livejournal.com/, you'll see them explaining that stuff is going wrong in the usual, customer service, understated way.

From my perspective, something is wrong with either the load balancers or the databases or something. Coz this is pretty ridiculous. Even the paid users are getting poor response right now.

this is unusual

[denizsarikaya.livejournal.com]

Erm, this week has been pretty bad. And tonight is the worst I've seen barring when LJ was attacked pretty effectively two months ago.

If you check out http://status.livejournal.com/, you'll see them explaining that stuff is going wrong in the usual, customer service, understated way.

From my perspective, something is wrong with either the load balancers or the databases or something. Coz this is pretty ridiculous. Even the paid users are getting poor response right now.

Oh, the status message has changed. Before, it was talking about how things had been bad, they'd found the probs in the servers and it would hopefully get fixed soon, but don't be surprised at continuing delays. Yeah, you get the drift.

[sps.livejournal.com]

Well, I just had a look at the source code.

I suppose it could be worse. But... it's a philosophical dog, as far as I can see, I can't imagine that it could really be made scalable no matter what you did.

this is unusual

[denizsarikaya.livejournal.com]

Erm, this week has been pretty bad. And tonight is the worst I've seen barring when LJ was attacked pretty effectively two months ago.

If you check out http://status.livejournal.com/, you'll see them explaining that stuff is going wrong in the usual, customer service, understated way.

From my perspective, something is wrong with either the load balancers or the databases or something. Coz this is pretty ridiculous. Even the paid users are getting poor response right now.

Oh, the status message has changed. Before, it was talking about how things had been bad, they'd found the probs in the servers and it would hopefully get fixed soon, but don't be surprised at continuing delays. Yeah, you get the drift.

Oh, my, I just got a "database unavailable" message while trying to post this comment. Yep, things seem to be spectacularly FUBARed.