Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TIKV Percolator 事务模型,事务 keys prewrite 全部成功后,tikv 和 tidb 节点挂了,这个事务后续还会被 commit 吗?
We know that in the Percolator transaction model, as long as the primary key commits successfully, even if all the nodes related to the transaction go down, the other keys can still be committed later without affecting the transaction.
But if the primary key goes down before committing and the corresponding TiDB node also goes down, and the lock TTL of all keys in the transaction has not expired.
At this time, will the resolve lock process of other transactions help commit this transaction? Or can it only choose to roll back after the lock TTL expires?
In the Async Commit transaction, since the primary key lock contains pointers to the secondary keys, the resolve lock should be able to help commit, right?