Shulou(Shulou.com)05/31 Report--

This article introduces the knowledge of "how to solve the session waiting caused by MySQL metadata lock". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

When adding a partition at the end of the month, a table found a card there, entered the corresponding instance and found a large number of metadata locks and so on.

The reason for this problem is:

After a session before the system performed the operation of the related table, the session was not submitted, and the metadata lock that occupied the table change was not released.

The solution is to query information_schema.trx to kill the empty transaction so that it releases the table metadata lock.

Kill 532427

Kill 540047

This is the end of the content of "how to solve the session waiting caused by MySQL metadata lock". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.