vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/das/umn/das_11_0080.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.0 KiB
Raw Permalink Blame History

InnoDB Lock Query

Scenarios

  • InnoDB lock status management allows you to diagnose conflicts during execution of transactions or sessions with a few clicks. By querying the lock status, you can obtain the lock-holding and lock-wait information of transactions, such as the transaction status, session ID, locked table, and locked data range.
  • InnoDB Lock Query is currently in open beta testing.

Procedure

  1. On the top menu bar, choose Intelligent O&M > InnoDB Lock Query. If there is no transaction waiting for a lock, click Refresh to view the latest lock query information.
  2. On the displayed page, the lock-holding and lock-wait information is displayed if a transaction is waiting for a lock.
    Figure 1 Querying the InnoDB lock
  3. Move the cursor above an icon to view its detailed information.
    Figure 2 Lock details
  4. Click the lock-holding or lock-wait icon. A dialog box for killing the session is displayed.
    Figure 3 Killing sessions
    • The default lock wait timeout is 50s. You can modify the innodb_lock_wait_timeout parameter to change the timeout value.
    • The SQL window execution timeout is 300s.
Parent topic: Intelligent O&M