[
https://issues.apache.org/jira/browse/IGNITE-20052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20052:
-------------------------------------
Description:
h3. Motivation
It is not only useless, but also harmful to keep locks on an expired primary
because corresponding commitTimestamps are either calculated or the transaction
will be aborted.
h3. Definition of Done
* All local partition specific locks are released on self primary replica
expiration.
h3. Implementation Notes
* It's required to introduce local onPrimaryExpired callback.
* An open question here is how to detect whether a given primary hosted any
locks.
was:
h3. Motivation
It is not only useless, but also harmful to keep locks on an expired primary
because corresponding commitTimestamps are either calculated or the transaction
will be aborted.
h3. Definition of Done
> Release all locks locally on self primary replica expiration
> ------------------------------------------------------------
>
> Key: IGNITE-20052
> URL: https://issues.apache.org/jira/browse/IGNITE-20052
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3, transaction3_recovery, transactions
>
> h3. Motivation
> It is not only useless, but also harmful to keep locks on an expired primary
> because corresponding commitTimestamps are either calculated or the
> transaction will be aborted.
> h3. Definition of Done
> * All local partition specific locks are released on self primary replica
> expiration.
> h3. Implementation Notes
> * It's required to introduce local onPrimaryExpired callback.
> * An open question here is how to detect whether a given primary hosted any
> locks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
