This topic describes how to set a primary/standby synchronization strategy by configuring tenant parameter templates to enable data synchronization for tenants with different compatibility modes.
Overview
The primary/standby synchronization strategy supports dynamically matching tenants based on tenant parameter templates and performing primary/standby data synchronization. You can select the tenant parameter template that meets your business requirements, and the system will automatically synchronize the data of tenants that match this template to the standby instance.
Tenant parameter template: The system provides the following parameter templates, each corresponding to different business scenarios and compatibility modes:
Parameter TemplateDescriptionOLTP Simple Transactions Suitable for simple transaction processing scenarios, supporting MySQL and Oracle compatibility modes. OLTP Complex Transactions Suitable for complex transaction processing scenarios, supporting MySQL and Oracle compatibility modes. HTAP Mixed Workloads Suitable for hybrid transaction and analytical processing scenarios, supporting MySQL and Oracle compatibility modes. OLAP Online Analytics Suitable for online analytical processing scenarios, supporting MySQL and Oracle compatibility modes. NoSQL Suitable for NoSQL scenarios, supporting HBase API and Table API compatibility modes. Note
- This feature is available only to allowlisted users. Contact technical support to enable it.
- The system will dynamically match tenants based on the selected parameter template. Only tenants that match the template will undergo primary/standby synchronization.
Compatibility mode: The compatibility mode of a tenant determines its data storage format and access method. Currently, the MySQL compatibility mode, Oracle compatibility mode, HBase API compatibility mode, and Table API compatibility mode are supported. Different parameter templates correspond to different compatibility modes. When setting the synchronization strategy, ensure that the tenant compatibility modes of the primary and standby instances are consistent.
Prerequisites
A primary instance and a standby instance have been created, and both are in the Running state. For more information, see Create a standby instance.
Tenants under the primary and standby instances have been created.
You have Project Admin and Instance Admin permissions.
Procedure
Log in to OceanBase Cloud.
In the left-side navigation pane, click Instances.
In the instance list, find the target cluster, click the arrow to the left of the instance to expand the instance tenant information. Then click the target tenant name to enter the Tenant Workspace.
Click Deployment diagram > Configure Primary-Standby Sync Strategy.
In the dialog box that appears, view the current tenant parameter template and the matched tenant information.
Tenant Parameter Template: Select the parameter template to synchronize. The system will automatically match the corresponding tenants based on the selected template.
Tenant List: View the tenant information matched under the current parameter template, including the tenant name/ID, parameter template, and compatibility mode.
After confirming the configuration is correct, click OK.
In the pop-up confirmation dialog box, review the notes, enter
confirmto confirm the operation, and click OK to complete the primary-standby synchronization strategy settings.Note
- If you cancel a parameter template, the standby tenants and their backup data that have been synchronized under this template will be deleted. Features that depend on standby tenants, such as global addresses and read/write splitting, will also become invalid.
- When you add a parameter template to the policy, the system creates a corresponding tenant in the standby instance for each tenant that uses the template.
- The operation to cancel a parameter template is irreversible. Please proceed with caution.
Related operations
View the primary and standby instance workspace information. For details, see Primary and standby instance workspace.
Create a standby instance. For details, see Create a standby instance.