[
https://issues.apache.org/jira/browse/IGNITE-25270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17982687#comment-17982687
]
Vladislav Pyatkov commented on IGNITE-25270:
--------------------------------------------
The final discussion focuses on the linked list in the MVPartition store. This
list connects all write intents and is stored in the same tree as the data.
In this case, all write intents remain available after a node restart.
> Come up with solution that allow persisting pending entries and does not have
> a performance impact
> --------------------------------------------------------------------------------------------------
>
> Key: IGNITE-25270
> URL: https://issues.apache.org/jira/browse/IGNITE-25270
> Project: Ignite
> Issue Type: Test
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. Motivation
> Our transaction protocol needs to know which entries were used in a
> transaction in a specific partition to switch their state from a write intent
> to a regular entry.
> {code:title=StorageUpdateHandler}
> /** A container for rows that were inserted, updated or removed. */
> private final PendingRows pendingRows = new PendingRows();
> {code}
> The set of the rows is in volatile storage (they disappear after the node
> restart). It leads to issues like IGNITE-25079.
> h3. Definition of done
> Write a document where a solution would be described.
> Jira tasks should be created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
