Configuring the Read/Write Status

Scenarios

You can change the read/write status of your instance to meet different workload requirements. Two modes are available: read-only and read/write.

• Read-only

  This mode restricts all data modification operations on the instance after it is set to read-only.

• Read/Write

  This is the default mode. If an instance is in the read-only state, you can switch it back to read/write mode to resume write operations.

Constraints

• This operation cannot be performed when the instance is in any of the following statuses: Creating, Changing instance specifications, Frozen, and Abnormal.
• Once an instance is set to read-only, data cannot be written into the instance.

Precautions

• Before enabling read-only mode, ensure that no write operations are occurring to avoid data inconsistency.
• After an instance is set to read-only, account and database management operations (on the Accounts and Databases page) remain available on the console.
• Once an instance is set to read-only, data writes are restricted for standard users. Setting an instance to read-only during large transactions or DDL operations may time out and fail.
• If you switch the status to read/write successfully but the instance remains read-only, check whether the instance is involved in a DRS migration task.
• If an instance becomes read-only due to other causes (such as DRS migration), you cannot restore it to read/write using this feature.
• This function only changes the read/write status of the primary instance. Read replicas remain in read-only mode.

Procedure

1. Log in to the TaurusDB console.
2. Click in the upper left corner and select a region.
3. On the Instances page, click the instance name to go to the Basic Information page.
4. In the Configuration area, click Configure under the Read/Write Permissions field.
5. In the displayed dialog box, configure the read/write status and click OK.
   Figure 1 Configuring the read/write status