About Database Options for Commit Protocols

The default setting for the commit database option is remote:1. However, NuoDB recommends that you use the safe commit protocol.

All transaction engines that serve a particular database should use the same commit protocol. Failure to observe this can cause consistency problems because clients are connecting to database processes that have different durability settings.

The following table shows the durability and performance tradeoffs for the commit protocols when journaling is enabled. If you do not require durability and if you are concerned primarily about performance then you would typically specify the commit local option. While the commit safe option is the only setting that guarantees durability, the remote and region settings provide progressively more protection from data loss if there is a database process failure.

Database Commit Options

Durability Performance






You can specify the commit database option in NuoDB Manager and in the Automation Console. See NuoDB Manager, Overview of Using the Automation Console and Database Options for more information.