There is "canceling statement due to lock timeout" prompt when I use antdb

I'm a new user of antdb and I always some problems while using it. Today I found there is "canceling statement due to lock timeout" prompt when I use antdb, how can I deal with it?

The lock occupied by a long transaction has not been released, and a new transaction requests a lock on the same object.
This error will be reported when the time set by lock_timeout is reached.
The client needs to commit or roll back the transaction in time, and long transactions are a very resource-consuming behavior for the database, so please try to avoid them.

--Check the status of the lock table
select locktype,relation::regclass as relation,virtualxid as vxid,transactionid as xid,virtualtransaction vxid2,pid,mode,granted from adb_locks where granted = 'f';
--view long transactions that take longer than 5 minutes to execute
select datname,pid,usename,client_addr,query,backend_start,xact_start,now()-xact_start xact_duration,query_start,now()-query_start query_duration,state from adb_stat_activity where state<>$$idle$$ and now()-xact_start > interval $$5 min$$ order by xact_start;
--kill long transaction. The 2 ways are as follows (PID is the pid return value from the above sql statement query):
method one:
SELECT adb_cancel_backend(PID);
(This method can only kill select queries, and does not work for update, delete and DML)

method two:
SELECT adb_terminate_backend(PID);
This can kill off various operations (select, update, delete, drop, etc.)

If there is no lock information related to the table in adb_locks, then you need to go to each datanode to see if there are two phases of outstanding transactions hanging there, query view: select * from adb_prepared_xacts.
Based on the time value of the prepared field to determine whether there is an abnormal transaction, the so-called abnormal, meet the following conditions:

The prepared field value shows a time that is longer than the current time, for example, more than the expected execution time of a single statement.
On every query, there are always some transactions existing all the time.

In general, these transactions are considered abnormal transactions. The status of this transaction can be queried on each node: select adb_xact_status(50996670) ;, with the parameter value of T removed from the gid value in adb_prepared_xacts.

If the transaction has been committed on GTMCOORD, the transaction needs to be committed on this node: commit 'T784168121'.
If the transaction is not committed on GTMCOORD, you need to roll back the transaction on this node: rollback prepared 'T784168121'.

The above operation needs to be executed on the database corresponding to the transaction, as determined by the value of the database column in adb_prepared_xacts.

A batch operation statement can be generated with the following statement:

select 'rollback prepared '''||gid||''';' 
from adb_prepared_xacts 
where  to_char(prepared,'yyyy-mm-dd hh24:mi') ='2020-01-01 14:30'
and database = 'db1'; 

Hope it helps you.