[
https://issues.apache.org/jira/browse/IGNITE-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806887#comment-17806887
]
Vladislav Pyatkov commented on IGNITE-21061:
--------------------------------------------
LGTM
> Durable cleanup requires additional replication group command
> -------------------------------------------------------------
>
> Key: IGNITE-21061
> URL: https://issues.apache.org/jira/browse/IGNITE-21061
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Kirill Sizov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> After locks are released, it is required to write the information to
> transaction persistent storage and replicate it on all commit partition
> replication group nodes. That is performed by the replication command
> ({{MarkLocksReleasedCommand}}). As a result, we have an additional
> replication command for the entire transaction process.
> h3. Implementation notes
> In my opinion, we can resolve this situation in the transaction resolution
> procedure ({{OrphanDetector}}). It just needs to do nothing additional:
> either release the locks by durable finish from the transaction coordinator
> or release them by recovery by {{OrphanDetector}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
