Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
1.2.5
-
None
Description
A table lock caused by a failed truncate will not be cleared even after a complete cluster restart:
Table LockID Process PID Session Txn CreationTime State DBRoots
|
dm_temp.tablename 1 DDLProc 5444 775 573937 Thu Nov 14 20:17:18 2019 LOADING 1,2
|
A cleartablelock will probably remove it, but it is not proper behaviour that a tablelock survives a cluster restart.
The table remains locked, affecting normal production workflow as data can't be inserted until the lock is cleared.