OceanBase Database provides two protection modes called maximum performance and maximum protection. You can switch between two modes.
Maximum performance
It is the default protection mode. Maximum performance ensures the performance of the primary cluster to the utmost extent and protects your data. In this mode, OceanBase immediately commits transactions after REDO logs persist in the primary cluster. OceanBase asynchronously synchronizes REDO logs to the standby clusters without blocking the transaction commit of the primary cluster. Therefore, the synchronization latency of the standby clusters does not affect the performance of the primary cluster.
The configurations of active/standby databases allow multiple standby clusters to run in maximum performance mode.
Maximum protection
This mode provides the highest level of data protection and prevents data loss when the primary cluster fails. In this mode, you need to ensure the persistence of REDO logs on the primary cluster and the highly consistent standby cluster, before committing the transaction.
The configurations of primary/standby databases allow only one standby cluster to run in the maximum performance mode. If the standby cluster in the maximum protection mode is unavailable, the primary cluster stops responding to data modification requests to prevent data loss.