Page History

...

• ConsistentCutStartRecord: record is written to WAL in moment when CC starts ConsistentCut starts on a local node. It helps to limit amout of active transactions to check. But there is no strict guarantee for all transactions belonged to the BEFORE side to be physically committed be committed before ConsistentCutStartRecord, and vice versa. This is the reason for having ConsistentCutFinishRecord.
• ConsistentCutFinishRecord: This record is written to WAL after Consistent Cut stopped analyzing active transactions and storing them in a particular bucket (BEFORE or AFTER).

It guarantees that the BEFORE side consist of:
1. transactions committed before ConsistentCutStartRecord and weren't included into ConsistentCutFinishRecord#after();
2. transactions committed between ConsistentCutStartRecord and ConsistentCutFinishRecord and were included into ConsistentCutFinishRecord#before().

It guarantees that the AFTER side consist of:
1. transactions physically committed transactions committed before ConsistentCutStartRecord and were included into ConsistentCutFinishRecord#after();
2. transactions physically committed after ConsistentCutStartRecord and weren't included into ConsistentCutFinishRecord#before().

...