Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Code Reviews Meta
Q&A
Posts Tags Edits
Ask Question

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on How do I track down intermittent locks in a MySQL database?

Post

How do I track down intermittent locks in a MySQL database?

+3
−0

Currently, we have a CRUD plus reporting application that talks to one MySQL database. Intermittently users will report locks when searching, currently, I can only get the approximate time of when that happens (accurate to the minute). The stored procedures on the other hand are logged to the millisecond.

So far I have not been able to trigger the issue, and the notifications by the users of the problem are not close enough to real-time to see what queries are running when the lock is happening.

One idea so far would to be to turn on all query logging the next time it happens since the locks seem to be clustered.

Are there other strategies for finding which queries are causing intermittent locks?

mysql database-locking
posted about 4 years ago
4y ago by Alexei‭
user card
Charlie Brumbaugh‭
1025 reputation 37 6 170 16
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (4 comments)
General comments
Alexei‭ wrote about 4 years ago
copy link

Ref. "we have a CRUD plus reporting application that talks to one MySQL database" - is there any way to use a separate database for the reporting application? Another way is to prevent the reports selects from locking the operational tables by using a "no-lock" option (SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED ; ), but this can lead to incorrect data. The best approach is still to have a separation between the operational database and the reporting one.

Charlie Brumbaugh‭ wrote about 4 years ago
copy link

@Alexei I don't think its the reports, but rather inserts crossing paths with the selects. The reports used to cause locks, but that was fixed by breaking the queries into chunks and then doing the calculations outside of the DB.

Alexei‭ wrote about 4 years ago
copy link

@Charlie Brumbaugh‭ Yes, the underlying technical issue is indeed having inserts and selects in the same time. That is why reporting typically has its own database where some aggregates can be recalculated and one almost never gets into trouble like this.

ghost-in-the-zsh‭ wrote about 4 years ago
copy link

@Alexei: Did you consider logging in the app, so that you can better correlate what the app is doing and when? That'd be my approach.