Advanced
Тема интерфейса

Modifying RabbitMQ Instance Specifications

After creating a RabbitMQ instance, you can increase or decrease its specifications. For details, see Table 1.

Table 1 Supported specification changes (for RabbitMQ 3.x.x)

Instance Type

Modified Object

Increase

Decrease

Cluster

Brokers

×

Storage space

×

Broker flavor

Single-node

Brokers

×

×

Storage space

×

Broker flavor

Impact

Table 2 Impact of specification modification

Modified Object

Impact

Brokers

  • Services may temporarily stutter during the modification. Ensure that your client can auto-reconnect. Modify specifications during off-peak hours.
  • The entire modification takes about 10 minutes.

Storage space

  • Storage space expansion does not affect services.
  • Available storage space = Actual storage space – Storage space for storing logs – Disk formatting loss For example, if the storage space is expanded to 700 GB, the storage space for storing logs is 100 GB, and the disk formatting loss is 7 GB, then the available storage space after capacity expansion will be 593 GB.
  • The total change duration is within 5 minutes.

Broker flavor

  • For single-node RabbitMQ 3.x.x instances and cluster instances without mirrored/quorum queues configured, services may stutter for several minutes during the modification. Ensure that your client can auto-reconnect. Modify specifications during off-peak hours.
  • For cluster RabbitMQ 3.x.x instances configured with mirrored/quorum queues, services may stutter for several seconds during the modification. Ensure that your client can auto-reconnect. Modify specifications during off-peak hours.
  • Brokers will be restarted in sequence during an instance change, which depends on the number of brokers. The change duration per single broker is 5–10 minutes. The total change duration = Single change duration × Number of brokers.

Notes and Constraints

  • To ensure that the instance runs properly, do not perform other operations on the instance during the modification.
  • The price may change after the modification.

Prerequisites

A RabbitMQ instance has been created and is in the Running state.

Modifying RabbitMQ Instance Specifications

  1. Log in to the console.
  2. In the upper left corner, click and select a region.
  3. Click and choose Application > Distributed Message Service for RabbitMQ to open the console of DMS for RabbitMQ.
  4. Modify the instance specifications using either of the following methods:

    • In the row containing the desired instance, choose More > Modify Specifications.
    • Click the desired RabbitMQ instance to view its details. In the upper right corner, choose More > Modify Specifications.

  5. Specify the required storage space, number of brokers, or bandwidth.

    • Expand the storage space.
      1. For Change By, select Storage. For Storage space per broker, specify a new storage space, and click Next. The storage space range varies by instance specifications. For details, see Specifications.
      2. Confirm the configurations and click Submit.
      3. Return to the instance list and check whether the change succeeded.
        • If the instance status has changed from Changing to Running, the change succeeded. View the new storage space (Storage space per broker x Number of brokers) in the Used/Available Storage Space (GB) column in the instance list.
        • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.

          Instances in the Change failed state cannot be modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations. If the status does not change to Running, contact customer service.

    • Add brokers.
      1. For Modify By, select Brokers. Then, enter the number of brokers. The broker quantity range varies by instance specifications. For details, see Specifications. If public access has been enabled, configure EIPs for the new brokers. Then click Next.
      2. Confirm the configurations and click Submit.
      3. Return to the instance list and check whether the change succeeded.
        • If the instance status has changed from Changing to Running, the change succeeded. You can check the new broker quantity in the Flavor column.
        • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.

          Instances in the Change failed state cannot be modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations. If the status does not change to Running, contact customer service.

    • Increase or decrease the broker flavor.
      1. For Modify By, select Broker Flavor. Then, select a new flavor and click Next.
      2. Confirm the configurations and click Submit.
      3. Return to the instance list and check whether the change succeeded.
        • If the instance status has changed from Changing to Running, the change succeeded. You can check the new broker flavor in the Flavor column.
        • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.

          Instances in the Change failed state cannot be modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations. If the status does not change to Running, contact customer service.

  6. Click Next, confirm the details, and click Submit.