Destiny

2002 readers

1 users here now

A community for Bungie's FPS looter-shooter MMO Destiny/Destiny 2

Rules:

Keep things civil. No hate speech, NSFW content, personal attacks, witch hunting, etc.
Do not discuss or share any leaks, datamined information, etc. No spoilers
Keep things on topic
No low effort posts, self-promotion, ads, or spam

Please report any comments or posts you think violate the rules. We regularly check reports and will take action if needed.

Resources:

Bungie.net for official forums, patch notes, blogs, and more
The official Destiny 2 Companion app for both iOS and Android
D2 Checklist to track weekly content
light.gg, a database of weapons and items
Destiny Item Manager to manage your vault and inventory
Destiny 2 Armor Picker to manage armor and stats
Destiny Tracker to track player stats
Trials Report to view player stats for Trials of Osiris

Creators:

Datto for guides, general and PvE-focused gameplay, and discussion
My name is Byf for in-depth lore videos
CoolGuy for in-depth weapon and armor reviews
Aztecross for general gameplay, builds, and more
ninjy for weapon damage testing

Other Lemmy Destiny Communities:

Destiny 2 Builds for character builds
LowSodiumDestiny for a salt-free Destiny community

founded 2 years ago

MODERATORS

oryx

rae

jontree255

This Week In Destiny 6/29/2023 (www.bungie.net)

submitted 1 year ago* (last edited 1 year ago) by jontree255 to c/destiny

7 comments fedilink hide all child comments

Lots of info in this one about the past month or so of server instability and some insight into what's been causing it.

I'll try to TL;DR/ELI5 this but I encourage everyone to read the article:

There is a service called "Claims" that helps run Destiny 2. It "syncs" the Destiny 2 game client to the game servers to "save" your progress. Changes were made to Claims before Lightfall to help it handle more traffic but it's not working as expected. Claims keeps getting interrupted for various reasons, which puts your game client out of sync with the server, forcing a disconnect.
"...Claims handles a tremendous amount of volume, routing every single kill, orb, or unit of Glimmer in Destiny 2 to the correct recipient."
Normally to fix issues like this they do a rolling restart to the Claims service, which causes disconnects but not downtime. This isn't working and they have to bring the whole Claims system down at the same time to restart. Without Claims online Destiny 2 cannot run, hence the repeated emergency downtime.
They are working to fix this issue and have listed specific patches over the next few months where they're targeting fixes:
- Mid Season 21 Update (7.1.5)
- Season 22 Launch (7.2.0)
- Season 23 Launch (7.3.0)
They're emphasizing that this is not something they can fix overnight or quickly. They also emphasize that the process of fixing it could potentially introduce more instability. They're implementing a lot of tracking, alerting, and testing tools to help them figure out a fix.

Next week will have increased drop rates for Exotic fish!

After that the TWID goes into the regular community stuff.

Sounds like they really screwed up with whatever they did pre-Lightfall if it's taking them nearly a year to fix. I'm curious to learn what the root cause was and how it was missed during testing. As an IT person it's interesting for me to see these kinds of case studies and the kind of stuff you have to deal with when you're working on something that has the scale of Destiny 2.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago

On one hand, I feel that frustration from server issues when I just want to play Destiny.

On the other hand, nobody's forcing me or anyone else to play Destiny. Just our own sense of FOMO that devs love taking advantage of.

Best of luck to the backend team. They're probably putting up with loads of technical debt and other problems.