It also explains why players were having so many issues with progress, too. Not exactly the recipe for a fun weekend, that. During this time, we also saw we could make configuration improvements to our database event logging, which is necessary to restore a healthy state in case of database failure, so we completed those, and undertook further root cause analysis. Our game servers were observing the disconnect from the database and immediately attempted to reconnect, repeatedly, which meant the database never had time to catch up on the work we had completed because it was too busy handling a continuous stream of connection attempts by game servers. On Sunday, though, it became clear what we’d done on Saturday wasn’t enough–we saw an even higher increase in traffic, causing us to hit another outage. We decided to roll back that Friday update we’d previously deployed, hoping that would ease the load on the servers leading into Sunday while also giving us the space to investigate deeper into the root cause. This was exacerbated by an update we had rolled out the previous day intended to enhance performance around game creation–these two factors combined overloaded our global database, causing it to time out. This was a new threshold that our servers had not experienced at all, not even at launch,” Blizzard explained.
“On Saturday morning Pacific time, we suffered a global outage due to a sudden, significant surge in traffic. Which sounds all well and good - until that central database gets overloaded and the whole system, much like the engineers working on it, needs a nap. These regional databases periodically send information back to the central database, so that way Blizzard has a singular record (with backups) of your thicc Level 88 Barbarians, Necromancers and so on. The global database also has a back-up in case the main fails,” Blizzard wrote. “Most of your in-game actions are performed against this regional database because it’s faster, and your character is “locked” there to maintain the individual character record integrity. This is needed because there’s too many people playing Diablo 2 to just continually upload everyone’s data to a single, central point. It’s not an individual server per se, but a cluster of servers that service an entire region.Īnyway, these servers all have their own regional databases that store the data of the characters that play on them. If you’ve played any Activision or Blizzard multiplayer game over the last few decades, you’ll know that you generally login to a set of servers as close to your location as humanly possible. The first major problem outlined by the team is how players’ characters and data is stored. It’s a massive explainer on all the issues facing Diablo 2: Resurrected players lately, and it’s so extensive because the problems aren’t caused by a single issue but a mix, ranging from an inability to deal with the game’s popularity, its architecture, and even down to the fact that players are just way more efficient at smashing Diablo into the dust in 2021.
And by the sounds of things, the poor server engineers must be absolutely hating life.įirst up: any time a developer posts a blog that surpasses 2,000 words, you know the shit has really hit the fan. For the last week, players have faced constant login issues and outages. Diablo 2: Resurrected launched, it’s authentic as all hell - but then the D2 servers took an instant trip to the Seventh Circle.
0 kommentar(er)
