The situation turned sour on Monday

To help ease the load, Blizzard rolled back the Friday update, but the strategy was not sufficient. A bigger rush of traffic caused another delay on Sunday. "We reached out to our third-party partners for help as well," PezRadar said.

To help ease the D2R Items load, Blizzard rolled back the Friday update, but the strategy was not sufficient. A bigger rush of traffic caused another delay on Sunday. "We reached out to our third-party partners for help as well," PezRadar said.

The situation turned sour on Monday, when Blizzard implemented fixes to Diablo 2's backup database, then tried to make the switch. Once the switch was completed the database continued to run its backup processes, but it was not able to handle queries from servers located elsewhere.

This issue was rectified on Tuesday, however another record-breaking number of concurrent players same day resulted in further "degraded performance of the database," which database engineers are still working to resolve.

The issue is so serious that the Diablo 2: Resurrected team has recruited engineers from different parts of Blizzard to help fix smaller problems , while it focuses on "core Server issues."

It is interesting to note that Blizzard's wish to preserve an original Diablo 2 experience in the remake is at the root of all these problems.

One "legacy service" in particular handles critical functions including "game creation/joining, updating/reading/filtering game lists D2R Ladder Items Buy, verifying game server health, and reading characters from the database."


xiuyun hao

56 Blog posts

Comments