Data Admin Service
Data Admin Service
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Logging In to the DAS Console
- Adding Login Information
- Logging In to a Database
- Modifying Login Information
- Deleting Login Information
- Logging In to Databases Shared by Others
- MySQL DB Instance Management (Development Tool)
- RDS for PostgreSQL Instance Management (Development Tool)
- DDS DB Instance Management (Development Tool)
- Distributed DDM DB Instance Management (Development Tool)
- Intelligent O&M
- Audit
- Change History
- Best Practices
-
FAQs
- Product Consulting
-
Connection Management (Development Tool)
- What Should I Do If I Can't Connect to My DB Instance Due to Insufficient Permissions?
- What Should I Do If I Can't Connect to My RDS for MySQL Instance?
- What Should I Do If I Can't Connect to My ECS (MySQL) Instance?
- What Should I Do If I Can't Connect to My RDS for PostgreSQL Instance?
- What Should I Do If I Can't Connect to My ECS (PostgreSQL) Instance?
- What Should I Do If I Can't Connect to My DDS Instance?
- What Should I Do If I Can't Connect to My DDM Instance?
- How Do I View and Modify ECS Security Group Rules?
- How Do I View and Modify Firewall Rules?
- Usage
- Service Support
- Change History
- Videos
Help Center/
Data Admin Service/
User Guide/
Intelligent O&M/
MySQL DB Instances/
Locks and Transactions/
Metadata Locks
Metadata Locks
Updated on 2023-03-07 GMT+08:00
Overview
- Metadata locks (MDLs) are used to ensure consistency between DDL and DML operations. Usually, DDL operations require MDL write locks. Once an MDL lock occurs, it can have a significant impact on your database because all subsequent operations (SELECT, DML, and DDL operations) on the target table will be blocked, causing a backlog of connections.
- The system displays database MDL locks in real time. With these locks, you can quickly locate MDL problems and terminate the sessions holding MDL locks, so that blocked operations can be restored.
NOTE:
- This feature does not support DML locks. You can view and analyze them on the InnoDB Locks page.
- Currently, this feature is available only for MySQL 5.6 and 5.7.
- A maximum of 1,000 records can be displayed.
Procedure
- Log in to the DAS console.
- On the Overview page, click Go to Intelligent O&M.
- Select the target instance and click Details.
- Choose Locks and Transactions > Metadata Locks.
- Select a lock status and type, and enter a database name, table name, and session ID as needed. Then, click Query.
- In the query result, check whether there are sessions that hold MDL locks. If yes, select the sessions as required and click Kill Session.
Parent topic: Locks and Transactions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.