[
https://issues.apache.org/jira/browse/IGNITE-20004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov resolved IGNITE-20004.
------------------------------------
Fix Version/s: None
Resolution: Duplicate
> Implement durable unlock within same primary
> --------------------------------------------
>
> Key: IGNITE-20004
> URL: https://issues.apache.org/jira/browse/IGNITE-20004
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Kirill Sizov
> Priority: Major
> Labels: ignite-3, transaction, transaction3_recovery
> Fix For: None
>
>
> h3. 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
> h3. 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.
> h3. Implemention Notes
> Durable recursive
> {code:java}
> replicaService.invoke(recipientNode, FACTORY.txCleanupReplicaRequest(){code}
> until success or loss of recipientNode(enlisted primary) are expected.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
