Page History

...

1. This node starts new DistributedProcess over whole baseline topology (failed if any node in BLT is down):
   
   1. Local node increments local ConsistentCutVersion, put it into ConsistentCutStartRequestthat is the InitMessage for the process.
   2. Every node on receiving this message compares received and local version, and if received is greater it prepares a ConsistentCut future.
   3. On receiving the new ConsistentCutVersion every node inits local ConsistentCut and starts signing TxMessages (see below) with new version.
   4. A node can receive new ConsistentCutVersion by both TxMessage and by ConsistentCutStartRequest.
   5. By receiving new CutVersion this node triggers procedure immediately (before applying message, in case of receiving TxMessage).
   6. if it failed, or cut is inconsistent, or previous received version >= new version → notify reducer about issue (user command for creating recovery point failed).

Consistent and

...

inconsistent Cuts

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

...