Troubleshooting database module
how a platform for introduction in troubleshooting database
design Page II
1 the first piece of content
designed to
return to the front by processlist
1 filter thread of sleep and slave dump thread
2 in accordance with the time to sort in reverse chronological order
3 adds the lock keyword filtration
analysis
1 by the time most time-consuming positioning time of slow SQL
2 to see if there MDL keyword lock lead to blocking subsequent request
2 second block content
designed
to classify statistics for DB database processlist by
analyzing
a possible existence of such circumstances, different business library there is one instance, the connection according to statistics so different location service DB of
3 third block content
designed
to classify statistics for the total number to access the database through processlist
analyzed
by statistical non-sleep process and the maximum number of links contrast to locate whether the connections sleep leads to depletion of threads
4 fourth block content
designed
for statistical affairs for the locks held by innodb_trx table
analysis
transaction 1 is being executed, locks held, may lead to wait for other transactions, lock design unreasonable
2 uncommitted transactions for a long time, may lead to Waiting for other transactions
III summarizes
Question 1 platform is when the database is not connected can not be analyzed, which is a little less than (case number of connections depletion may occur)
2 only capture transient, not prior to analysis of the issues, the future will be addressed