Original Post — Direct link

Again issues on EUW

Can’t queue up anymore, get kicked out of queue automatically after a minute.

It’s getting beyond ridiculous man, sure an issue from time to time is understandable, but this is the 4th/5th time in the span of what? 1-2 days??

External link →
8 months ago - /u/spawndog - Direct link

This is the same issue as occurred 12 hours ago which we have not found the root cause of. A full platform restart returns to service which we will do once existing games have ended.

After an update to the database software in a few regions it has a small chance to perma lock a table. If you cannot read a game ID you cannot start the game

8 months ago - /u/spawndog - Direct link

Originally posted by iwanofski

MySQL still or was that only for account data? Did Riot issue a bug report that I can view?

MySQL 8 update is the suspected catalyst, the current version is hitting end of life this year which forced our hand. As we do not know the root cause it could be a bad code pattern that has existed for years on our side.

Sorry, I haven't seen a bug report outside of ticker status.

8 months ago - /u/spawndog - Direct link

Originally posted by Voidz918

Do none of these issues appear outside of euw?

We have not rolled out the change everywhere but its occured in multiple places we did such as Taiwan and Oceania

8 months ago - /u/spawndog - Direct link

Originally posted by CrossXhunteR

Would you be able to say if this might have been causing issues with Legends of Runeterra this past week or so?

From the incident report 7 days ago for Runeterra: "Due to the occurrence of a Database Deadlock, The game kicked players out of Games and The Client."

That does look suspiciously similar. We can see if there is a connection. Nice catch!

8 months ago - /u/spawndog - Direct link

Originally posted by HFPerplexity

How do you not know the root cause? Do you guys not have any observability within your architecture?

Our telemetry/observability costs are eye watering. An issue is too little signal to noise which we are working on.

We are a little closer to a root cause. A default value in the MySQL update for locking behavior changed and triggered the issue. We're rolling that fix out now