[jira] [Created] (IGNITE-15316) Read Repair may see inconsistent entry at tx cache when it is consistent but updated right before the check

["Anton Vinogradov (Jira)" <ji...@apache.org>]

Anton Vinogradov created IGNITE-15316:
-----------------------------------------

             Summary: Read Repair may see inconsistent entry at tx cache when it is consistent but updated right before the check
                 Key: IGNITE-15316
                 URL: https://issues.apache.org/jira/browse/IGNITE-15316
             Project: Ignite
          Issue Type: Sub-task
            Reporter: Anton Vinogradov
            Assignee: Anton Vinogradov


Even at FULL_SYNC mode stale reads are possible from backups after the lock is obtained by "Read Repair" tx.
This is possible because (at previous tx) entry becomes unlocked on primary before tx committed on backups.
This is not a critical problem for Ignite in general but produces false positive "inconsistency state found" events and repairs.

Unlock relocation does not seems to be a proper fix, since it will cause a performance drop.
So, we should recheck values several times if an inconsistency is found, even when the lock is already obtained by "Read Repair".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)