Bark of the Dragon

December 1, 2006

“Consider the database load issue resolved…” NOT! :)

Filed under: Second Life,Updates — tomashausdorff @ 2:33 pm

I logged in briefly an hour or so after it was announced in the Linden Lab blog that the majority of the post-update database-related problems in Second Life had been resolved.

Initially, things looked good: search seemed to be working again, and I was able to teleport back to my home sim.  I then went to take a snapshot and send it as a postcard.  Unfortunately, the user interface failed to fill in my return address.  That particular field is uneditable: its supposed to be automatically generated by the client application.  Helpfully, the SL client told me that I hadn’t entered my return address..uhm, gee, thanks, but since I’m not actually permitted to edit that field, maybe that’s *your* fault?   I bug reported it, and then decided to see if perhaps it was something that only occurred immediately after teleporting.  So I logged off and logged back in…

Hmmm.   I’m not standing where I loggeded off at.  I’ve been “bumped” to another locale, back to a place I was at one step earlier in this saga.  And it seems that my clothing is missing…well, actually, my entire body- all I am is a floating head and some legs.  Okay, that kind of thing happens now and then- let’s see if we can teleport back home…nope.  Perhaps my sim is down- that happens too, sometimes.  How about that snapshot?  What with my body being invisible and all, it might be sort of comical.  Nope, same error when I try to send it as a post card.  Let’s see if we can find any land for sale…oopsie, the search interface is down again.

I really feel sorry for the Linden Lab folks.  I imagine many of them have packed up and gone home after 20 or more hours of working on problems, feeling relief that things are working properly again before the weekend.  Just wait until they are awakened from their all too brief but well deserved naps to fix yet another database failure…

Maybe its time to look at some transactional message queuing infrastructure between the databases?   I can only speculate where their current challenges may lie…but keeping all of the data stores in sync may be at the root of the current scalability problems.  Alternately, it could be some horrific database design flaw, or something as simple as inadequate database server performance- memory/disk/network/processor upgrades could possibly fix that.

Update: Quite literally as I was typing this, the LL folks (Torley!) posted an update referring to continuing database problems.  Frustrating for them, no doubt. 


Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

%d bloggers like this: