[IGNITE-17949] Full rebalance must be restricted when it causes any updates loss.

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ise
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Anton Vinogradov
• Created: 21/Oct/22 12:20
• Updated: 21/Oct/22 12:26

Description

For example, it's

• ok to replace partition's copy B with partition's copy A when
  A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111], hwm=120],
  because A contains whole B.
• NOT ok to replace B with A when
  A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111], hwm=148],
  when update 142 will be lost.

But, currently, full (any) rebalance takes into account only LWM, and B will be replaced with A in both cases (where historical rebalance is impossible).

Issue Links

• relates to: IGNITE-17738 Cluster must be able to fix the partition inconsistency on restart/node_join by itself