infoschema, executor: Add the deadlock table

[MyonKeminta]

What problem does this PR solve?

Problem Summary: As part of Lock View , there will be a new system table named DEAD_LOCK that shows information about recent several deadlock error.

What is changed and how it works?

What's Changed:

• A module named deadlockhistory is introduced, located in the util directory like stmtsummary. It contains a global instance of a queue to collect deadlock events in FIFO manner.
• An OnDeadlock callback is added to LockCtx, and is called at the time the deadlock error is received from TiKV but before pessimsticRollback.
• A new table DEAD_LOCK in information schema is added to show the collected deadlock events in the TiDB node, and also a cluster version CLUSTER_DEAD_LOCK that shows deadlock information from all TiDB nodes in the cluster.
  • Each row of the DEAD_LOCK table represents one of the transactions that causes the deadlock, and rows with the same DEADLOCK_ID forms a complete deadlock event.
  • For CLUSTER_DEAD_LOCK table, rows with the same (INSTANCE, DEADLOCK_ID) forms a deadlock event since the DEADLOCK_ID is not unique among different TiDB nodes.

Note that the ALL_SQLS field in our design is not ye implemented in this PR. It relies on the TIDB_TRX table, and also the current PR is already too large.

Example:

/* init */ drop table if exists t;
-- init >> 0 rows affected
/* init */ create table t (id int primary key, v int);
-- init >> 0 rows affected
/* init */ insert into t values (1, 10), (2, 20), (3, 30);
-- init >> 3 rows affected
/* t1:wait */ begin;
-- t1 >> 0 rows affected
/* t1 */ update t set v = 11 where id = 1;
-- t1 >> 1 rows affected
/* t2 */ begin;
-- t2 >> 0 rows affected
/* t2 */ update t set v = 21 where id = 2;
-- t2 >> 1 rows affected
/* t1:wait */ update t set v = 12 where id = 2;
-- t1 >> blocked
/* t2 */ update t set v = 22 where id = 1;
-- t2 >> E1213: Deadlock found when trying to get lock; try restarting transaction
-- t1 >> resumed
-- t1 >> 1 rows affected
/* t1 */ rollback;
-- t1 >> 0 rows affected
/* t2 */ rollback;
-- t2 >> 0 rows affected
/* t3:wait */ select * from information_schema.deadlocks;
-- t3 >> +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
-- t3    | DEADLOCK ID |         OCCUR TIME         | RETRYABLE |  TRY LOCK TRX ID   |                        CURRENT SQL DIGEST                        |                  KEY                   | ALL SQLS |  TRX HOLDING LOCK  |
-- t3    +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
-- t3    |           1 | 2021-05-19 10:48:09.567305 |         0 | 425045860169023490 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000002 | NULL     | 425045860169023491 |
-- t3    |           1 | 2021-05-19 10:48:09.567305 |         0 | 425045860169023491 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000001 | NULL     | 425045860169023490 |
-- t3    +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
/* t3:wait */ select l.deadlock_id, l.occur_time, l.try_lock_trx_id, l.trx_holding_lock, s.digest_text from information_schema.deadlocks as l left join information_schema.statements_summary as s on l.current_sql_digest = s.digest;
-- t3 >> +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+
-- t3    | DEADLOCK ID |         OCCUR TIME         |  TRY LOCK TRX ID   |  TRX HOLDING LOCK  |               DIGEST TEXT               |
-- t3    +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+
-- t3    |           1 | 2021-05-19 10:48:09.567305 | 425045860169023490 | 425045860169023491 | update `t` set `v` = ? where `id` = ? ; |
-- t3    |           1 | 2021-05-19 10:48:09.567305 | 425045860169023491 | 425045860169023490 | update `t` set `v` = ? where `id` = ? ; |
-- t3    +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+
/* t1:wait */ begin;
-- t1 >> 0 rows affected
/* t1 */ update t set v = 11 where id = 1;
-- t1 >> 1 rows affected
/* t2 */ begin;
-- t2 >> 0 rows affected
/* t2 */ update t set v = 21 where id = 2;
-- t2 >> 1 rows affected
/* t3 */ begin;
-- t3 >> 0 rows affected
/* t3 */ update t set v = 31 where id = 3;
-- t3 >> 1 rows affected
/* t1:wait */ update t set v = 12 where id = 2;
-- t1 >> blocked
/* t2 */ update t set v = 22 where id = 3;
-- t2 >> blocked
/* t3 */ update t set v = 32 where id = 1;
-- t3 >> E1213: Deadlock found when trying to get lock; try restarting transaction
-- t2 >> resumed
-- t2 >> 1 rows affected
/* t2 */ rollback;
-- t2 >> 0 rows affected
-- t1 >> resumed
-- t1 >> 1 rows affected
/* t1 */ rollback;
-- t1 >> 0 rows affected
/* t3 */ rollback;
-- t3 >> 0 rows affected
/* t4:wait */ select * from information_schema.deadlocks;
-- t4 >> +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
-- t4    | DEADLOCK ID |         OCCUR TIME         | RETRYABLE |  TRY LOCK TRX ID   |                        CURRENT SQL DIGEST                        |                  KEY                   | ALL SQLS |  TRX HOLDING LOCK  |
-- t4    +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
-- t4    |           1 | 2021-05-19 10:48:09.567305 |         0 | 425045860169023490 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000002 | NULL     | 425045860169023491 |
-- t4    |           1 | 2021-05-19 10:48:09.567305 |         0 | 425045860169023491 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000001 | NULL     | 425045860169023490 |
-- t4    |           2 | 2021-05-19 10:48:27.592010 |         0 | 425045862528319493 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000002 | NULL     | 425045862528319494 |
-- t4    |           2 | 2021-05-19 10:48:27.592010 |         0 | 425045862528319494 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000003 | NULL     | 425045862528319495 |
-- t4    |           2 | 2021-05-19 10:48:27.592010 |         0 | 425045862528319495 | 22230766411edb40f27a68dadefc63c6c6970d5827f1e5e22fc97be2c4d8350d | 7480000000000000355F728000000000000001 | NULL     | 425045862528319493 |
-- t4    +-------------+----------------------------+-----------+--------------------+------------------------------------------------------------------+----------------------------------------+----------+--------------------+
/* t4:wait */ select l.deadlock_id, l.occur_time, l.try_lock_trx_id, l.trx_holding_lock, s.digest_text from information_schema.deadlocks as l left join information_schema.statements_summary as s on l.current_sql_digest = s.digest;
-- t4 >> +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+
-- t4    | DEADLOCK ID |         OCCUR TIME         |  TRY LOCK TRX ID   |  TRX HOLDING LOCK  |               DIGEST TEXT               |
-- t4    +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+
-- t4    |           1 | 2021-05-19 10:48:09.567305 | 425045860169023490 | 425045860169023491 | update `t` set `v` = ? where `id` = ? ; |
-- t4    |           1 | 2021-05-19 10:48:09.567305 | 425045860169023491 | 425045860169023490 | update `t` set `v` = ? where `id` = ? ; |
-- t4    |           2 | 2021-05-19 10:48:27.592010 | 425045862528319493 | 425045862528319494 | update `t` set `v` = ? where `id` = ? ; |
-- t4    |           2 | 2021-05-19 10:48:27.592010 | 425045862528319494 | 425045862528319495 | update `t` set `v` = ? where `id` = ? ; |
-- t4    |           2 | 2021-05-19 10:48:27.592010 | 425045862528319495 | 425045862528319493 | update `t` set `v` = ? where `id` = ? ; |
-- t4    +-------------+----------------------------+--------------------+--------------------+-----------------------------------------+

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
  • TODO
• Requires executor, store: Pass the SQL digest down to pessimistic lock request #24380 to be merged first

Check List

Tests

• Unit test (TODO)
• Integration test (TODO)

Side effects

• Performance regression
  • Consumes more CPU
  • Consumes more MEM

Release note

• Adds table DEAD_LOCK and CLUSTER_DEAD_LOCK table that provides information about recent several deadlock events

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• cfzjywxk
• youjiali1995

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[MyonKeminta]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 816a573

[MyonKeminta]

/run-integration-ddl-test
/run-unit-test

[MyonKeminta]

/run-unit-test

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what's changed

Or if the count of mainly changed packages are more than 3, use

• *: what's changed

[ti-chi-bot]

@MyonKeminta: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.