...
- Consistent Cut
+ Simple algorithm - requires only some read-write locks to sync threads, and doesn't affect performance much.
+ Doesn't require to much additional space - it just writing few additional messages to WAL.
- Requires time to recovery (applying every message from WAL to system) that depends on how many operations need to be restored.
- Requires additional storage to persist WAL archives.
- Doesn't restore ATOMIC caches. (but can be fixed with ReadRepair). - Incremental physical snapshots
- High disk IO usage for preparing snapshots.
- Current implementation of snapshots requires PME, that affects performance much.
+ Fast recovering, doesn't depend on amount operations to restore (WAL-free). - MVCC
- Ignite failed to support MVCC, very hard to implement.
...
{"serverDuration": 156, "requestCorrelationId": "ee4d0b718360c783"}