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