Help Center/ TaurusDB/ User Guide/ Read Replicas/ Creating a Read Replica
Updated on 2025-03-28 GMT+08:00

Creating a Read Replica

Scenarios

Read replicas of a DB instance are used to enhance instance capabilities and reduce the read pressure on the primary node.

After a DB instance is created, you can add read replicas.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page, choose Database > GaussDB(for MySQL).
  4. On the Instances page, locate the instance that you want to create read replicas for and choose More > Create Read Replica in the Operation column.
  5. On the displayed page, configure related parameters.

    Table 1 Parameter description

    Parameter

    Description

    Failover Priority

    Failover priority ranges from 1 for the first priority to 16 for the last priority. This priority determines the order in which read replicas are promoted when recovering from a primary node failure. Read replicas with the same priority have a same probability of being promoted to the new primary node. You can configure a failover priority for up to 9 read replicas, and the default priority for the remaining read replicas is -1, indicating these read replicas cannot be promoted to primary. You can change the failover priority of a read replica.

    Quantity

    A DB instance can contain up to 15 read replicas.

  6. For a yearly/monthly instance, click Buy Now and select a payment mode.
  7. For a pay-per-use instance, click Next.
  8. Check the read replica settings.

    • If you need to modify the settings, click Previous.
    • If you do not need to modify the settings, click Submit.

  9. View the new read replica information in the Node List area of the Basic Information page. You can also promote a read replica to primary or delete a read replica.