TiDB does not clean table lock if restart on OOM

[marsishandsome]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

tidb config

# enable-table-lock is used to control the table lock feature. The default value is false, indicating that the table lock feature is disabled.
enable-table-lock: true

# delay-clean-table-lock is used to control the time (milliseconds) of delay before unlocking the table in abnormal situations.
delay-clean-table-lock: 60000

1. lock tables test.tt write local
2. kill -9 tidb
3. start tidb
4. wait 60 seconds
5. lock tables test.tt write local
6. get error: Table tt was lock in WRITE LOCAL by server

2. What did you expect to see? (Required)

TiDB should clean table lock if restart on OOM

3. What did you see instead (Required)

success to lock table

4. What is your TiDB version? (Required)

3.0.14

[ekexium]

/label sig/DDL

[ekexium]

/label sig/DDL

[sre-bot]

Integrity check：
component RCA symptom affect_version fix_version fields are empty
@crazycs520
Please comment /info to get template

[ti-srebot]

Please edit this comment to complete the following information

Bug

1. Root Cause Analysis (RCA)

This bug only affects the TiDB cluster which config has enable-table-lock = true, indicates the enable the table lock feature.

If tidb-server was been kill -9 (such as OOM that killed by the system), the killed tidb-server will have no change to release the held table lock, so those table lock will not been released unless the user uses admin cleanup table lock [table_name] statement to force clean table lock.

2. Symptom

Lock table statement execute failed.

3. Minimal steps to reproduce the bug (optional)

4. Solution (optional)

• Upgrade

5. W/A (Workaround)

Uses admin cleanup table lock [table_name] statement to force release table lock.

6. Affected versions

[v3.0.14:v3.0.18],
[v3.1.0:v3.1.2],
[v4.0.0:v4.0.6]

7. Fixed versions

v3.0.19
v3.1.3
v4.0.7

[seiya-annie]

Please edit this comment to complete the following information

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA)

This bug only affects the TiDB cluster which config has enable-table-lock = true, indicates the enable the table lock feature.

If tidb-server was been kill -9 (such as OOM that killed by the system), the killed tidb-server will have no change to release the held table lock, so those table lock will not been released unless the user uses admin cleanup table lock [table_name] statement to force clean table lock.

2. Symptom

Lock table statement execute failed.

3. All Trigger Conditions

see in issue body

4. Workaround (optional)

Uses admin cleanup table lock [table_name] statement to force release table lock.

5. Affected versions

[v3.0.14:v3.0.18],
[v3.1.0:v3.1.2],
[v4.0.0:v4.0.6]

6. Fixed versions

v3.0.19
v3.1.3
v4.0.7