[IGNITE-13003] Improve data loss handling

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8
• Fix Version/s: 2.9
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Alexey Scherbakov
• Reporter: Alexey Scherbakov
• Created: 12/May/20 12:03
• Updated: 12/Jan/22 23:23
• Resolved: 22/May/20 05:30

Description

Current implementation of data loss handling in Ignite has pitfalls which have to be fixed.

Details can be found by reading a dev-list discussion [1]

[1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Data-loss-handling-improvements-td47310.html
[2] https://lists.apache.org/thread.html/r1d01c11e973c3f3ada3f76505058dc15953fe04dfadbaa89c055e392%40%3Cdev.ignite.apache.org%3E

Issue Links

• duplicates: IGNITE-1605 Provide stronger data loss check
• incorporates: IGNITE-13053 resetLostPartitions is not working if invoked from a node where a cache not started
• incorporates: IGNITE-13054 Prevent nodes with stale data joining the active topology.
• incorporates: IGNITE-13051 Optimized affinity switch on baseline node left is broken for client topology and MVCC
• is related to: IGNITE-16273 Regression:CacheInvalidStateException: Failed to execute query because cache partition has been lostPart
• links to: GitHub Pull Request #7800
• links to: Pull Request #7800