On premise only: see Durability A replicated environment makes it possible to increase an application's transaction commit guarantees by committing changes to its replicas on the network. ReplicaAckPolicy defines the policy for how such network commits are handled.

Since

5.3.0

Enumeration Members

Enumeration Members

ALL: "ALL"

All replicas must acknowledge that they have committed the transaction. This policy should be selected only if your replication group has a small number of replicas, and those replicas are on extremely reliable networks and servers.

Since

5.3.0

NONE: "NONE"

No transaction commit acknowledgments are required and the master will never wait for replica acknowledgments. In this case, transaction durability is determined entirely by the type of commit that is being performed on the master.

Since

5.3.0

SIMPLE_MAJORITY: "SIMPLE_MAJORITY"

A simple majority of replicas must acknowledge that they have committed the transaction. This acknowledgment policy, in conjunction with an election policy which requires at least a simple majority, ensures that the changes made by the transaction remains durable if a new election is held.

Since

5.3.0

Generated using TypeDoc