Parameter | Description |
Billing mode | When the billing mode of the read-write instance compute specifications is monthly subscription, the read-only analysis engine supports both the monthly subscription and pay-as-you-go billing modes; when the billing mode of the read-write instance compute specifications is pay-as-you-go, the read-only analysis engine only supports the pay-as-you-go billing mode. |
Instance engine | Select an engine for the current read-only instance. Currently, both the InnoDB and LibraDB engines are supported. Select the LibraDB engine here. |
Region | Select a region for the read-only analysis engine instance. Currently, you can only select the same region as that of the TDSQL-C for MySQL read-write instance. |
Availability zone | Select an availability zone for the read-only analysis engine instance. Currently, you can select an availability zone different from that of the read-write instance or other read-only instances under the TDSQL-C for MySQL cluster. Due to the cross-AZ capability of the VPC, the network overhead is less than or equal to 100 ms in cross-AZ access scenarios. |
Network | VPC by default, same as that of the read-write instance under the TDSQL-C for MySQL cluster. The subnet is an optional subnet of the specified availability zone. You can also select a VPC network different from that of the read-write instance. |
Security group | For the read-only analysis engine instance, you can select a security group different from that of the corresponding TDSQL-C for MySQL cluster to control the instance access policy. |
Custom port | You can set a custom port number for accessing the read-only analysis engine instance. The default is 2000. Port range: 1024–65534 |
Data load mode | Indicates the method for loading data from a read-write instance under the corresponding TDSQL-C for MySQL cluster into the read-only analysis engine. The default is entire instance synchronization. The default value is No objects. Full load: All data objects in the read-write instance are loaded into the read-only analysis engine (unsupported objects are directly skipped). Partial objects: Only selected objects are loaded into the read-only analysis engine. No objects: No objects are loaded, but only an empty read-only analysis engine is created. Users need to set it up themselves later. |
Instance specifications | Select instance specifications for the read-only analysis engine. Different instance specifications offer different performance experiences. Since data analysis or complex SQL execution consumes a lot of computing resources, the instance specifications of the read-only analysis engine are relatively large. Additionally, in high-concurrency data writing scenarios, if the read-only analysis engine needs to ensure primary-secondary data consistency, it will also consume some resources. You should select specifications based on the actual business situations. |
Disk type | Currently only high I/O SSD disks are supported. |
Disk specifications | Since the read-only analysis engine instance currently does not use the shared storage of the TDSQL-C for MySQL cluster, you need to separately purchase disk space to store columnar storage data. Therefore, the disk space here should be selected separately and will be billed separately. The minimum disk specification is 100 GB, and the maximum disk specification depends on the specification of the selected instance. Specifications on the actual purchase page shall prevail. |
Instance name | Custom instance name, which can be named after creation or immediately named. |
Quantity | Select the purchase quantity as needed. Up to 6 read-only analysis engines can be purchased. |
Was this page helpful?