Enabling Read-Only Analysis Engine

Last updated:2026-01-12 17:16:53

Enabling Read-Only Analysis Engine

Last updated: 2026-01-12 17:16:53

This document introduces how to create a read-only analysis engine instance for TencentDB for MySQL.
Prerequisites
You have prepared a TencentDB for MySQL instance. See Creating a MySQL Instance.
The instance is running.
Operation Steps
Notes:
Currently, you can create a read-only analysis engine only under an existing cluster in the provisioned resource instance mode, but cannot create it under a cluster being created.
The creation of a read-only analysis engine is only supported for MySQL 5.7 and MySQL 8.0 kernel versions.
The creation of a read-only analysis engine is not supported for instances using the RocksDB kernel.
The creation of a read-only analysis engine is only supported for instances with two-node or three-node architectures.
1. Log in to the MySQL console.
2. In the instance list, locate the instance to which you want to add a read-only analysis engine. Click the Instance ID or Manage in the operation column to enter the instance management page.
3. Select the Read-only Instance page and click Create to enter the read-only instance creation page.
Note:
You can also go to the instance details page, click + RO Analytics Engine or Create below the architecture diagram of the instance to go to the read-only instance creation page.
﻿
4. Complete the following configuration and click Buy Now.
Parameter
Description
Instance Engine
Select the engine for the current read-only instance. Currently, both InnoDB and LibraDB engines are supported. In this case, select the LibraDB engine.
Specify Analytic RO Group
Supports automatic assignment by the system, creating an RO group, or selecting an existing RO group.
Automatic assignment by the system: If multiple instances are purchased at once, the system will assign a separate RO group to each instance. The weight distribution method is set to automatic assignment by the system by default.
Create an RO group: Creates an RO group. If multiple instances are purchased at once, all will be assigned to this RO group. The weight distribution method is set to automatic assignment by the system by default.
Existing RO group: Specifies an existing RO group. If multiple instances are purchased at once, all will be assigned to this RO group. The weight distribution method follows the RO group configuration: If the RO group is set to automatic assignment by the system, RO groups will be added automatically based on the purchased specifications; if it is set to custom assignment, the default weight is zero. Since instances in the same RO group share the same private IP address, they will also share the same security group settings in VPC networks. If you select an existing RO group, you will not be able to customize the security group during the purchasing process.
Note:
Analytical RO groups do not support capabilities such as delayed replica elimination upon exceeding latency thresholds. All other functionalities are consistent with those of standard RO groups.
Analytic RO Group Name
When creating an RO group, you need to specify a name for the new RO group. The name can include Chinese characters, English letters, digits, hyphens (-), underscores (_), and periods (.), and should be less than 60 characters in length.
Billing Mode
If the billing mode of the primary instance is monthly subscription, the read-only analysis engine supports either monthly subscription or pay-as-you-go billing mode. However, if the primary instance is billed under the pay-as-you-go mode, the read-only analysis engine only supports pay-as-you-go billing.
Region
Select the region where the read-only analysis engine instance resides. Currently, only the same region as the primary instance of TencentDB for MySQL is supported.
AZ
Select the availability zone where the read-only analysis engine instance resides. For the specific available zones, see the options shown on the actual page.
Instance Specification
Select the instance specification for the read-only analysis engine. Different specifications offer varying levels of performance. Since data analysis and complex SQL execution can consume significant computing resources, the instance specifications for the read-only analysis engine are relatively high. In high-concurrency data write scenarios, additional resources may also be consumed to ensure data consistency between the primary and secondary nodes. Choose the specification based on your actual business needs.
Hard Disk
Select the storage capacity of the hard disk. The minimum disk size is 100 GB, and the maximum limit depends on the selected instance specification. See the actual purchase page for available options.
Data Load Mode
Specifies how the read-only analysis engine loads data from the corresponding primary instance of TencentDB for MySQL. The default option is no objects.
All objects: Loads all data objects from the primary instance into the read-only analysis engine (unsupported objects will be automatically skipped).
Partial objects: Only the selected objects will be loaded into the read-only analysis engine. After selecting this option, you should specify the objects to be loaded in the section below.
No objects: No objects will be loaded. This option creates an empty read-only analysis engine instance, and you will need to configure data loading manually afterward.
Network
By default, the VPC is the same as that of the primary instance of TencentDB for MySQL, and the subnet is selected from the available subnets within the specified availability zone. It also supports deployment in a different VPC from the primary instance.
Security Group
You can select a security group different from that of the corresponding TencentDB for MySQL instance for the read-only analysis engine, in order to control its access policy.
Tag
Adds tags to the read-only analysis engine instance.
Instance Name
Customizes the instance name. You can choose naming after creation or immediate naming.
Instance Termination Protection
Choose whether to enable Instance Termination Protection. Once enabled, the instance cannot be terminated through the console or APIs.
Quantity
Select the quantity to purchase based on your actual business needs. You can purchase up to 6 read-only analysis engines.
5. After the purchase is completed, you will be redirected to the instance list. Once the instance status shows running, it is ready for use.

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Parameter	Description
Instance Engine	Select the engine for the current read-only instance. Currently, both InnoDB and LibraDB engines are supported. In this case, select the LibraDB engine.
Specify Analytic RO Group	Supports automatic assignment by the system, creating an RO group, or selecting an existing RO group. Automatic assignment by the system: If multiple instances are purchased at once, the system will assign a separate RO group to each instance. The weight distribution method is set to automatic assignment by the system by default. Create an RO group: Creates an RO group. If multiple instances are purchased at once, all will be assigned to this RO group. The weight distribution method is set to automatic assignment by the system by default. Existing RO group: Specifies an existing RO group. If multiple instances are purchased at once, all will be assigned to this RO group. The weight distribution method follows the RO group configuration: If the RO group is set to automatic assignment by the system, RO groups will be added automatically based on the purchased specifications; if it is set to custom assignment, the default weight is zero. Since instances in the same RO group share the same private IP address, they will also share the same security group settings in VPC networks. If you select an existing RO group, you will not be able to customize the security group during the purchasing process. Note: Analytical RO groups do not support capabilities such as delayed replica elimination upon exceeding latency thresholds. All other functionalities are consistent with those of standard RO groups.
Analytic RO Group Name	When creating an RO group, you need to specify a name for the new RO group. The name can include Chinese characters, English letters, digits, hyphens (-), underscores (_), and periods (.), and should be less than 60 characters in length.
Billing Mode	If the billing mode of the primary instance is monthly subscription, the read-only analysis engine supports either monthly subscription or pay-as-you-go billing mode. However, if the primary instance is billed under the pay-as-you-go mode, the read-only analysis engine only supports pay-as-you-go billing.
Region	Select the region where the read-only analysis engine instance resides. Currently, only the same region as the primary instance of TencentDB for MySQL is supported.
AZ	Select the availability zone where the read-only analysis engine instance resides. For the specific available zones, see the options shown on the actual page.
Instance Specification	Select the instance specification for the read-only analysis engine. Different specifications offer varying levels of performance. Since data analysis and complex SQL execution can consume significant computing resources, the instance specifications for the read-only analysis engine are relatively high. In high-concurrency data write scenarios, additional resources may also be consumed to ensure data consistency between the primary and secondary nodes. Choose the specification based on your actual business needs.
Hard Disk	Select the storage capacity of the hard disk. The minimum disk size is 100 GB, and the maximum limit depends on the selected instance specification. See the actual purchase page for available options.
Data Load Mode	Specifies how the read-only analysis engine loads data from the corresponding primary instance of TencentDB for MySQL. The default option is no objects. All objects: Loads all data objects from the primary instance into the read-only analysis engine (unsupported objects will be automatically skipped). Partial objects: Only the selected objects will be loaded into the read-only analysis engine. After selecting this option, you should specify the objects to be loaded in the section below. No objects: No objects will be loaded. This option creates an empty read-only analysis engine instance, and you will need to configure data loading manually afterward.
Network	By default, the VPC is the same as that of the primary instance of TencentDB for MySQL, and the subnet is selected from the available subnets within the specified availability zone. It also supports deployment in a different VPC from the primary instance.
Security Group	You can select a security group different from that of the corresponding TencentDB for MySQL instance for the read-only analysis engine, in order to control its access policy.
Tag	Adds tags to the read-only analysis engine instance.
Instance Name	Customizes the instance name. You can choose naming after creation or immediate naming.
Instance Termination Protection	Choose whether to enable Instance Termination Protection. Once enabled, the instance cannot be terminated through the console or APIs.
Quantity	Select the quantity to purchase based on your actual business needs. You can purchase up to 6 read-only analysis engines.

tencent cloud

Prerequisites

Operation Steps