However, on Sunday it became apparent that what we'd done on the previous day wasn't enough. We noticed a larger growth in traffic, leading us to experience another downtime with D2R Items. Our game servers were observing the database's absence and immediately tried to connect, often which meant that the database never had time to complete the work we had completed since it was busy processing a constant stream requests to connect by game servers. In this period, we also noticed that we could improve the configuration of our data event log, which is vital to restore the health of the database in case of database failure, so we did these, and then conducted a further investigation into the root of the issue.
This isn't exactly the recipe for an enjoyable weekend. It also explains why players were having problems with their progress, too. You'd choose your character, play then play for a bit but the regional server could not communicate with the central database following an downtime. This meant it wasn't able to tell Diablo 2's the source from "ground truth" about the brand new equipment and XP that you'd accrued, making angry players lose some of the progress they'd made.
The problems got even worse from there. Diablo 2 servers came back online. Diablo 2 servers came back up and running, but they were not online during a time where the majority of players were online. So although the servers re-established quickly, they crashed almost instantly as soon as hundreds of thousands of Diablo 2 instances fired up.
And if the weekend was not great but what came next on Tuesday and Monday wasn't much better:This leads us into Monday, October 11 which was the day we made changes to the global databases. This led to another outage in which our backup database was mistakenly continuing to run its backup process, meaning that it spent the majority of the time trying to copy from the other database when it was supposed to handle requests from servers.
During this time, we discovered further issues, and we made further improvements-we found a since-deprecated-but-taxing query we could eliminate entirely from the database, we optimised eligibility checks for players when they join a game, further alleviating the load, and we have further performance improvements in testing as we speak. We also believe that we've solved the database-reconnect storms we were seeing, because we didn't observe it happen on Tuesday.
This is the point where I'm constantly hearing my brother's advice to me: "Never get into networking."Diablo 2 Resurrected down for Maintenance This May 17If you're trying log in into Diablo 2 Resurrected However, you aren't you, don't worry, Blizzard has caused Diablo 2 Resurrected Items Resurrected to go down and it's scheduled maintenance for this May 17.Diablo 2 Resurrected Down Status and Updates for May 17:The delay is expected to run for 2 hours, but that might take longer (as these things sometimes do).
