Page History

...

Consistent Cut, in terms of Ignite implementation, is such cut that correctly finished on all baseline nodes - ConsistentCutStartRecord and ConsistentCutFinishRecord are written.

"In-consistentInconsistent" Cut is such a cut when one or more baseline nodes hasn't wrote ConsistentCutFinishRecord. It's possible in case of cases:

1. any errors appeared during processing local Cut.

...

1. if a transaction is recovered with transaction recovery protocol (txCutVer is unknown).
2. if transaction finished in UNKNOWN state.
3. baseline topology change, Ignite nodes finishes local Cuts running in this moment, making them inconsistent.

ConsistentCutVersion

Every ignite nodes tracks current ConsistentCutVersion:

...