You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2025/04/30 10:36:00 UTC
[jira] [Updated] (IGNITE-25270) Come up with solution that allow persisting pending entries and does not have a performance impact
[ https://issues.apache.org/jira/browse/IGNITE-25270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladislav Pyatkov updated IGNITE-25270:
---------------------------------------
Description:
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.
> 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
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)