You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Pligin (Jira)" <ji...@apache.org> on 2026/04/07 08:06:00 UTC

[jira] [Resolved] (IGNITE-26019) Read from backup: write intents handling

     [ https://issues.apache.org/jira/browse/IGNITE-26019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Pligin resolved IGNITE-26019.
--------------------------------------
    Resolution: Fixed

> Read from backup: write intents handling
> ----------------------------------------
>
>                 Key: IGNITE-26019
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26019
>             Project: Ignite
>          Issue Type: Epic
>            Reporter: Vladimir Pligin
>            Priority: Major
>              Labels: ignite-3
>
> This is a follow-up activity after IGNITE-22468.
> Currently in case of slow replication from primary to backup (slower than TransactionConfigurationSchema#txnResourceTtl) users can have successful read transactions lacking parts of committed data when it goes through the backup flow. At the moment only SQL is affected as other calls don't run RO on backups.
> KV support for RO tx on backups is a separate item - https://issues.apache.org/jira/browse/IGNITE-25619



--
This message was sent by Atlassian Jira
(v8.20.10#820010)