tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TDSQL-C for MySQL
    Documentation
    Download PDF

    Enabling Read-Only Analysis Engine

    Last updated: 2024-12-13 17:24:23
    Download PDF
      Currently, read-only analysis engine instances can be created only under clusters in the provisioned resource instance mode, but cannot be created under clusters in the Serverless instance mode. This document introduces how to create a read-only analysis engine instance in TDSQL-C for MySQL.

      Prerequisites

      You have prepared a cluster in the provisioned resource instance mode. See Creating Cluster.
      The cluster is in the running status.

      Directions

      Note:
      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.
      1. Log in to the TDSQL-C MySQL console and click the target cluster in the cluster list on the left to enter the cluster management page.
      2. On the cluster management page, click the button after Create Analysis Engine to enter the page for creating a read-only analysis engine.
      3. The purchase window for a read-only analysis engine is almost the same as that for a read-only instance. You can select an engine freely. Detailed parameter information is as shown in the table below:
      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 TXSQL 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.
      Synchronization object
      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.
      Entire instance synchronization: All data objects in the read-write instance are loaded into the read-only analysis engine (unsupported objects are directly skipped).
      Specified objects: Only selected objects are loaded into the read-only analysis engine.
      Setting after creation: 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.
      Instance name
      Custom instance name.
      Duration/quantity
      Select a purchase duration and quantity based on actual business situations.
      4. After completing the above configuration, click Purchase Now. After payment, return to the cluster list. Once the instance status is shown as Running, the instance can be used normally.
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy