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

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2020/07/20 12:45:00 UTC

[jira] [Updated] (IGNITE-13271) Add new type of WAL records to track/debug atomic updates on backup nodes

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

Vyacheslav Koptilin updated IGNITE-13271:
-----------------------------------------
    Fix Version/s: 2.10

> Add new type of WAL records to track/debug atomic updates on backup nodes
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-13271
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13271
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Major
>             Fix For: 2.10
>
>
> Currently, updates of the same key, for atomic caches, can arrive on backup nodes in a different order and the most actual only is applied.
> For instance:
> Primary node: update1 -> update2 -> update3
> Backup node: update1-> update3 -> update2(which is skipped)
> It seems it would be useful to track/log these updates for testing purposes.



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