Rolling restart

Template:Needs Translation/KB/de Template:Needs Translation/KB/es Template:Needs Translation/KB/el Template:Needs Translation/KB/fr Template:Needs Translation/KB/he Template:Needs Translation/KB/it Template:Needs Translation/KB/ja Template:Needs Translation/KB/ko Template:Needs Translation/KB/nl Template:Needs Translation/KB/hu Template:Needs Translation/KB/no Template:Needs Translation/KB/da Template:Needs Translation/KB/sv Template:Needs Translation/KB/tr Template:Needs Translation/KB/pl Template:Needs Translation/KB/pt Template:Needs Translation/KB/ru Template:Needs Translation/KB/th Template:Needs Translation/KB/uk Template:Needs Translation/KB/zh-Hans Template:Needs Translation/KB/zh-Hant

/KB

add versioning

What is a "rolling restart"?

The Second Life world has thousands upon thousands of Regions running on a great many servers. Due to the sheer logistics involved with managing them, not to mention all our Residents who'd prefer Second Life to have as much uptime as possible, it's unfeasible to restart every Region at the same time when an upgrade is needed.

Think of a rolling restart like a wave: it doesn't occur everywhere simultaneously, but travels from one place to another. As some servers are restarting, others have already been restarted several minutes ago, and are coming online shortly. Thus, only a portion of Second Life is down at any one time.

Rolling restarts usually apply to all of Second Life, including Private Regions.

Specific details of how a rolling restart proceeds are sometimes announced on our Grid Status Reports page.