[IGNITE-20004] Implement durable unlock within same primary

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Labels: ignite-3 transaction transaction3_recovery
• Epic Link: Tx on unstable topology: commit partition recovery
• Assignee: Kirill Sizov
• Reporter: Alexander Lapin
• Created: 19/Jul/23 06:30
• Updated: 13/Oct/23 09:05
• Resolved: 13/Oct/23 09:03

Description

Motivation

It's required to release all acquired locks on transaction finish in a durable way. Such durability consists of two parts:

• Durable unlock within same primary.
• Durable unlock on primary change.

This ticket is about first part only. There's a counterpart ticket for the second part IGNITE-20002

Definition of Done

• All unreleased locks for the transactions that were finished are either released or corresponsing lockholder primary 've left the topology. Locks are volatile and are stored only on the primary replica, thus in case of lock-holder primary failure, all locks will be automatically released.

Implemention Notes

Durable recursive

replicaService.invoke(recipientNode, FACTORY.txCleanupReplicaRequest()

until success or loss of recipientNode(enlisted primary) are expected.

 

 

Issue Links

• relates to: IGNITE-20055 Durable txCleanupReplicaRequest send from the commit partition