Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- links to