About the Remote Commit Protocol

When a transaction engine (TE) receives a commit request, the TE asynchronously broadcasts the commit to all available nodes, (SMs and TEs).

Commit is the last action of a transaction to be journaled, therefore once the commit is durably stored to the journal, all actions of the transaction are durably stored to the journal and the transaction cannot be lost.

The remote commit with journaling means that a commit request has been received by at least one SM process and has been journaled. An acknowledgment that a commit has been completed is sent to the client only if and when a round trip to at least one SM process has been completed.

About the Remote:N Commit Protocol

The specified number (N) of storage managers must acknowledge the transaction before it is committed. This commit protocol provides durability only when exactly N storage managers are running.