These two factors combined overwhelmed our database globally, causing it to be delayed d2r items for sale. We chose to roll back the Friday update that we had previously deployed in the hope of easing the load on the servers over the course of Sunday, while also giving us the space to explore the root cause.
On Sunday, though, it became clear what we had done on Saturday was not enough. We also saw an additional number of requests, which led us to experience another downtime. Our game servers were aware of the database's absence and attempted to connect, repeatedly, which meant the database never had time to complete the work that we'd done due to it being too busy managing a constant stream connections made by game servers.
In this period, we also noticed that we could implement configuration changes to our log of database events, which is vital to bring the database back to an optimal state in the event of database failure, so we did these, and undertook further root cause analysis.
This isn't exactly the recipe for a fun weekend, that. It's also the reason players were experiencing so many issues with progression, too. The player would select a character, launch a game, play for a while however the local server was unable to connect to the central database because of an downtime. Therefore, it was unable to inform Diablo 2's source in "ground truth" regarding the latest equipment and XP you'd gained, which led to frustrated players losing some of the progress they'd made.
The issue only got more serious from that point on. The Diablo 2 servers came back on the internet, but they did so during a period when most players were online--so even though they recovered rapidly diablo II resurrected items, they crashed nearly instantly as soon as millions of Diablo 2 instances fired up.
Share this page with your family and friends.