-
Task
-
Resolution: Done
-
Major
-
9.2.1.Final
-
None
-
Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1
We need a test that starts conflict resolution and then crashes a node or starts another merge, to verify that conflict resolution is properly interrupted or restarted as necessary.
HotRodMergeTest was unintentionally testing this by starting the 2nd test before the 1st test's merge finished in all the server caches, but we need something more deterministic in core.
- relates to
-
ISPN-9014 Conflict resolution consistent hash should not include nodes that are not in the merged cluster view
- Closed