Leonid Fedorov added a comment - 2024-04-05 12:24 The discussion with drrtuy highlighted these details. cpimport acquires several locks while importing the data, and it has different semantics. Blindly removing all the locks cpimport left after being killed could result in the loss of the table, and the only recourse would be to restore metadata from the backup. Some of the locks, and probably all of them if the table was empty and there is no risk of losing the data, could be released by a simple technique. We can replace cpimport with a bash script bearing the same name, rename the cpimport binary to dump all the lock names to a text file, and then invoke table lock cleaning after the cpimport operation. Thus, it seems possible to automate cleaning for some cases without requiring a significant investment of development time. However, achieving a complete resolution of the request may prove tricky.