Affects Version/s: None
Fix Version/s: None
Steps to reproduce:
1. Start a node.
2. Disable checkpoints.
3. Put some data.
4. Flush WAL.
5. Restart node.
6. Next put hangs sporadically forever awaiting for next topology that will never happens.
The issue caused by ClusterTopologyException thrown due to partition MOVING state, however it is expected partition to be in OWNING state.
The root cause is partition doesn't restore OWNING state after recover from WAL as it was not checkpointed or contains no data when checkpoint occurs (partition was in initial state).
Seems, forcing checkpoint before disabling it resolves the issue. See CacheMvccTxFailoverTest.testSingleNodeTxMissedCommitNoCheckpoint().