DelayPostUplift: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
='''<span style="color:#00528c">About</span>'''= | ='''<span style="color:#00528c">About</span>'''= | ||
In 2020, Linden Lab "uplifted" all the Second Life regions to the "AWS cloud". | In 2020, Linden Lab "uplifted" all the Second Life regions to the "AWS cloud", and the Linden Lab datacenter(s) were shut down by Mid-December of 2020. | ||
='''<span style="color:#00528c">The Problem</span>'''= | ='''<span style="color:#00528c">The Problem</span>'''= | ||
: The CasperTech databases still retain "records" of vendors, rental units AND dropboxes that were rezzed out on the OLD Linden Lab addresses (from their physical datacenter.) | |||
( | : Any of these items that have NOT "phoned home" since the Uplift (such as anything that has been Edit > Deleted inworld, but without a clean up bee run afterward) still has "ghosts" in the system. | ||
The good news is | : (And as you might have guessed, there's a lot!) | ||
='''<span style="color:#00528c">What This Means For You</span>'''= | |||
: Any items which have not been able to "phone home" '''WILL''' result in delays of 60 seconds PER ITEM that has had THAT profile being edited. | |||
: If you are adding a NEW product to your vendors, this means there will be a delay while ALL of your vendors are pinged (because the default "new item" status is in the default profile, which means it can and will appear on any vendor that is not set to a specific non-default profile.) | |||
: This is because the system is trying to contact the old items at a web address that '''no longer exists.''' | |||
: The good news is delays for YOU are only dependent on how many of YOUR items are "ghosted". | |||
='''<span style="color:#00528c">The Fix</span>'''= | ='''<span style="color:#00528c">The Fix</span>'''= | ||
: Run the appropriate UpgradeBee on "Check All" in ALL regions where you have had vendors, dropboxes and/or rental units rezzed out in the past. | |||
Run the appropriate UpgradeBee on "Check All" in ALL regions where you have had vendors, dropboxes and/or rental units rezzed out. | |||
: If you no longer have rez rights, you can WEAR the UpgradeBee, fly up to over 200m, click and use the "check all" function that way. | |||
: Until this is done, when you go to make updates to your stuff, the system will ALSO be checking the old URL's, and they will have an apx 60 second timeout PER ITEM that hasn't "phoned home" already (been clicked on or used.) | |||
Revision as of 16:20, 26 December 2020
About
In 2020, Linden Lab "uplifted" all the Second Life regions to the "AWS cloud", and the Linden Lab datacenter(s) were shut down by Mid-December of 2020.
The Problem
- The CasperTech databases still retain "records" of vendors, rental units AND dropboxes that were rezzed out on the OLD Linden Lab addresses (from their physical datacenter.)
- Any of these items that have NOT "phoned home" since the Uplift (such as anything that has been Edit > Deleted inworld, but without a clean up bee run afterward) still has "ghosts" in the system.
- (And as you might have guessed, there's a lot!)
What This Means For You
- Any items which have not been able to "phone home" WILL result in delays of 60 seconds PER ITEM that has had THAT profile being edited.
- If you are adding a NEW product to your vendors, this means there will be a delay while ALL of your vendors are pinged (because the default "new item" status is in the default profile, which means it can and will appear on any vendor that is not set to a specific non-default profile.)
- This is because the system is trying to contact the old items at a web address that no longer exists.
- The good news is delays for YOU are only dependent on how many of YOUR items are "ghosted".
The Fix
- Run the appropriate UpgradeBee on "Check All" in ALL regions where you have had vendors, dropboxes and/or rental units rezzed out in the past.
- If you no longer have rez rights, you can WEAR the UpgradeBee, fly up to over 200m, click and use the "check all" function that way.
- Until this is done, when you go to make updates to your stuff, the system will ALSO be checking the old URL's, and they will have an apx 60 second timeout PER ITEM that hasn't "phoned home" already (been clicked on or used.)