Rolling Restart to deploy 1.27.0

UPDATE #8 2009-07-14: The pilot roll is complete.

UPDATE #7 2009-07-14: The pilot roll is about to begin.

UPDATE #6 2009-07-13: Due to some bugs that showed up in the pilot regions and the desire for additional testing, we'll be re-doing the pilot roll on Tuesday. If that goes well, we're planning on doing the full roll on Wednesday and Thursday.

UPDATE #5 2009-07-09: The pilot roll is complete.

UPDATE #4 2009-07-09: The pilot roll has begun.

UPDATE #3 2009-07-08: Here are the 1.27 Release Notes:

UPDATE #2 2009-07-07: Due to the desire for additional testing, we are now targeting Thursday, 07/09 for the pilot roll instead of Wed, 07/08. I've updated the schedule below.

UPDATE 2009-07-07: Sorry, the pilot roll will be 500 simhosts, not 500 regions. Corrected below.

We will be deploying server version 1.27.0 to Second Life during the weeks of July 6th and July 13th. The rolling restart is scheduled to look like the following:

* Thu. 07/09, 7-10AM : a pilot roll of ~500 simhosts
* Tue. 07/14, 7-12AM : half of Second Life will be restarted
* Wed. 07/15, 7-12AM : the remainder of Second Life will be restarted

As with all of our server deploys, each region will be restarted once during one of the rolling restart periods. Most regions should be down no more than 5-10 minutes, although some fraction of the regions will take 20-30 minutes to upgrade. If your region stays down for more than 30 minutes, please contact support. Each region will receive warnings starting 5 minutes before that region is restarted.

Please provide a link to the release notes here and at the blog.

Awesome... The mainland sims have DESPERATELY needed rolling restarts for MONTHS now.. Once a month would be better to alleviate script lag buildup, but a little is better than nothing I guess.

Jules, the mainland has been restarted at or after may15 rolling out 1.26
the 1.27 release notes are not available yet, the 1.27 beta release note you can find at

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.27

No, I can't see the beta release notes there.

And I think Jules has a very good point there. I stumbled over the missing link as well when I read the announcement. Makes me wonder is there something to hide? Or does even Linden Labs themselves don't know what the new server version will bring? Or is this just another communication blunder.

Ok, we know what it is. But still...

release notes for beta versions -->

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.27

Just a simple remark .. i remember last year lots of french pple and sims organised events for the national day... 14th of july rolling restart is a good schedule ? could it be done on the 4th of july ?? (*gently grins*)

Here we go again.........

/me grabs some popcorn and a beer and waits for the drama to break out.

I'm not seeing anything in the notes about the group chat problems.

I was reading else where that is a server problem with group chat failure increasing 60% over the 1.25 version.

Any news on why this feature got removed, Dante? It was quite useful..

"Save object back to my inventory" was killed in 1.25, the reason given in those release notes was "this feature didn't always work as expected, and was the source of some confusion and potential content loss".

The JIRA asking to bring it back is http://jira.secondlife.com/browse/SVC-3947

Yes; especially disappointing given Sardonyx Linden's post:
https://blogs.secondlife.com/community/technology/blog/2009/07/01/a-status-update-on-group-chat

But, i guess it's ok that when he says "Later in this month", it comes along a little more than 2 days later.

But not MUCH later, Sardonyx! We're dyin' here!

Some interesting fixes. But more importantly, will there be a RR bear from Prospero?

Sadly, no. Prospero is no longer with LL.
.

Ah, missed that Nika, thanks. Well good luck with what will no doubt be many frustrating hours with the RRs and posting the same answers to the same questions in the forums Dante

I suppose if you ever get TP's working reliably this will become important lol

Will this address http://jira.secondlife.com/browse/SVC-3867 ?

There was also a permissions exploit based on it. Apparently in order to save the village they had to destroy it.

I suspect reliable TP and border crossing is going to require some deep refactoring of how objects move from one sim to another.

A single avatar crossing the border between Hollywood and Santa Catalina sims currently takes somewhere between 13 and 20 seconds to process on a good day. During this time the av will rubberband completely across the region it is entering and beyond.

This is broken.

A flying vehicle attempting to enter or leave the region containing Hau Koda Airport is a lost cause.

I haven't seen the teleport limitation discussed before... I'm relieved teleporting around in one region doesn't seem to cause problems, but teleporting between two regions does, and apparently if you keep trying to get out it'll even log you out?



Does anybody have any idea what brought this on?

For the past two days I have barely been able to port anywhere in the sim. It is very annoying to be limited to either flying and hit and miss or trying to port and either doing it or being told I can't.

Right now my drow avatar who is not dressed for public is lost in the sim not able to get home or where I want to port to.

One big problem is rapid fire teleporting with a wacky heavy attachment load. Rezzing is a big server-side bottleneck. Some sims have been getting mercilessly hammered by attacks based on that for months.

/me suspects this is as much LLNet as the sim itself.. Heavy prim/script load means big honkin' packets being transferred between sims and the way the sim just stalls - not a sim FPS drop but a real stall - feels like some sorta network problem.

/me also notices that the regession SVC-4142 is still unassigned.

Avatars are poofed into a sim atomically; the appearance, attachments, script states are all deserialized at once in one frame. I like to point the finger at the recent proliferation of resize scripts, even if they're not entirely at fault, just because I don't like them.