Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/#660 Rare mysql deadlock #723

Merged
merged 1 commit into from
Feb 24, 2021

Conversation

Askaholic
Copy link
Collaborator

@Askaholic Askaholic commented Feb 19, 2021

Can't really test it since it only happens rarely on production and probably only under high load.

Closes #660

@p4block
Copy link

p4block commented Feb 19, 2021

This may or may not be fixed magically with the move to MariaDB

try:
return await conn.execute(*args)
except OperationalError as e:
if any(msg in e.message for msg in (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I think

Suggested change
if any(msg in e.message for msg in (
if "Deadlock found" in e.message or "Lock wait timeout exceeded" in e.message:

is maybe less elegant but a bit easier to read, unless you expect that more strings will be added to the list of checks.

server/db/__init__.py Outdated Show resolved Hide resolved
@Askaholic Askaholic merged commit 8d95f77 into FAForever:develop Feb 24, 2021
@Askaholic Askaholic deleted the issue/#660-mysql-deadlock branch February 24, 2021 00:48
@Askaholic Askaholic changed the title Issue/#606 Rare mysql deadlock Issue/#660 Rare mysql deadlock Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rare deadlock prevents game results from being written
3 participants