vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/das/umn/das_05_0043.html
Wang , Deng Ke 0f41701050 DAS UMN Initial version 
Reviewed-by: gtema <artem.goncharov@gmail.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2022-10-18 12:51:00 +00:00

3.1 KiB
Raw Permalink Blame History

Metadata Locks

Overview

  • Metadata locks (MDLs) are used to ensure consistency between DDL and DML operations. Usually, DDL operations require MDL write locks. Once a DML 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 the 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.
    • This feature does not support DML locks. You can view and analyze them on the InnoDB Locks page.
    • Currently, this feature is available for only MySQL 5.6 and 5.7.
    • A maximum of 1,000 records can be displayed.
    • GaussDB(for MySQL) DB instances are currently not supported.

Procedure

  1. Log in to the DAS console using your username and password.
  2. On the Overview page, click Go to Intelligent O&M.
  3. Select the required instance and click Details to go to the Intelligent O&M overview page.
  4. Choose Locks and Transactions > Metadata Locks.
  5. Select a lock status and type, and enter a database name, table name, and session ID as needed. Then, click Query to query required sessions.
  6. In the query result, check whether there are sessions that hold MDL locks. If so, select the sessions and click Kill Session.
Parent topic: Locks and Transactions