All Products
Search
Document Center

ApsaraMQ for RocketMQ:Manage the lifecycle of an instance

更新時間:Aug 14, 2024

This topic describes how to manage an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance, including how to create an instance, upgrade or downgrade instance configurations, renew an instance, and unsubscribe from an instance.

Create an Enterprise Platinum Edition instance

You can create an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance in the ApsaraMQ for RocketMQ console by performing the following operations:

  1. Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar of the page that appears, select a region.

  2. On the Instances page, click Create Instance and follow the on-screen instructions to purchase an instance.

    • Instance Version: Select V4.0.

    • Instance Type: Select Enterprise Platinum Edition.

    • Product Type: Use the default value Subscription.

Upgrade or downgrade instance configurations

You can upgrade or downgrade the configurations of an existing Enterprise Platinum Edition instance based on your business requirements.

Impacts

  • During the upgrade or downgrade, transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. In most cases, transient connections do not affect business because the automatic reconnection mechanism is triggered on clients. However, exception logs are generated and message delay can occur.

  • Messages may be duplicated. We recommend that you perform message idempotence in advance. For more information, see Message idempotence.

  • During the upgrade or downgrade, do not manage resources in the ApsaraMQ for RocketMQ console. For example, do not create or delete topics.

  • If you access the ApsaraMQ for RocketMQ instance over HTTP, transient connections may occur or connection requests may be rejected. The issue lasts for less than 1 minute. Make sure that the reconnection mechanism is configured on clients.

We recommend that you use CloudMonitor to monitor important business. This way, you can obtain the status and metrics of your instance at the earliest opportunity during the upgrade or downgrade. For more information, see Configure the monitoring and alerting feature for risk warning.

Rules

Item

Description

Modifiable configurations

  • Peak TPS

  • Maximum topics

  • Message storage space

Effective period

The changes take effect in the current subscription cycle.

Impact on billing

  • When you upgrade the configurations of an Enterprise Platinum Edition instance, the system automatically calculates the fees that you must pay. You must pay the money before you complete the upgrade.

  • After you downgrade the configurations of an Enterprise Platinum Edition instance, the system refunds you the money that exceeds the price of the downgraded instance.

Operations

  1. Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar of the page that appears, select the region where your instance resides.

  2. On the Instances page, click the name of the instance that you want to manage. In the upper-right corner of the Instance Details page, click Upgrade or Downgrade.

Renew an instance

You can renew only ApsaraMQ for RocketMQ Enterprise Platinum Edition instances. You can select auto-renewal or manual renewal based on your business requirements.

Auto-renewal

If you want to use a service for a long time, you can enable the auto-renewal feature. After the auto-renewal feature is enabled, the system renews your resources before the resources expire to ensure that the resources and data are not deleted.

Auto-renewal rules

  • Auto-renewal is triggered nine days before an instance expires. If the first auto-renewal attempt fails, auto-renewal is triggered once a day until it succeeds or until one day before the instance expires.

  • The auto-renewal process starts at 08:00 (UTC+8) every day. However, an instance may be renewed after 08:00 because instances are automatically renewed in sequence. In most cases, an instance is renewed no later than 18:00 on the same day when auto-renewal starts.

  • Expiration time: If an instance expires at 00:00 on December 11, the day before the expiration date starts at 00:00 on December 10. The sixth day after the expiration date starts at 00:00 on December 17.

  • Auto-renewal is not triggered immediately after you enable the feature. Auto-renewal is triggered only at the fixed points in time that are described in the preceding items.

  • You must enable the auto-renewal feature before an instance expires. If you enable the auto-renewal feature after the instance expires, auto-renewal cannot be triggered.

  • If you enable the auto-renewal feature after 08:00 on the day before the expiration date, auto-renewal may not take effect. If you want to use the auto-renewal feature, we recommend that you enable the feature at your earliest opportunity.

Operations

  • Method 1: Enable the auto-renewal feature when purchasing an instance

    You can select Auto-renewal when you purchase an instance.

  • Method 2: Enable the auto-renewal feature in the Expenses and Costs console

    1. Log on to the ApsaraMQ for RocketMQ console. In the Basic Information section of the Instance Details page, obtain the ID of the instance.

    2. In the top navigation bar, choose Expenses > Renewal Management.

    3. On the Renewal page in the Expenses and Costs console, enable auto-renewal for the instance based on the obtained instance ID.

Manual renewal

If you want to continue using your ApsaraMQ for RocketMQ instance but auto-renewal is not enabled for the instance, you can manually renew the instance before it expires.

Limits

  • Limits on instances: You cannot renew an instance that has been expired for more than seven days.

  • Limits on renewal duration: You can renew an instance for one to nine months, one year, two years, or three years.

Operations

  1. Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar of the page that appears, select the region where your instance resides.

  2. On the Instances page, click the name of the instance that you want to manage. In the upper-right corner of the Instance Details page, click Renew.

Unsubscribe from an instance

Rules

  • ApsaraMQ for RocketMQ Enterprise Platinum Edition instances support partial refund. For more information, see Rules for unsubscribing from resources.

  • By default, the Post-expiration Action parameter of an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance is set to Delete Resource. The value specifies that the instance and its resources are deleted immediately after the instance expires or is unsubscribed.

  • If you set the Post-expiration Action parameter of an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance to Downgrade to Standard Edition, the instance is downgraded to Standard Edition and billed based on the pay-as-you-go billing method after the instance expires or is unsubscribed. For more information, see Change an instance from Enterprise Platinum Edition to Standard Edition.

  • You can view and modify the Post-expiration Action parameter of an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance on the Instance Details page in the ApsaraMQ for RocketMQ console.

Method

To unsubscribe from an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance, perform the following operations:

On the Unsubscribe page in the Fees and Costs console, set the Type parameter to Partial Refund and find the ApsaraMQ for RocketMQ instance from which you want to unsubscribe. Then, click Unsubscribe Resource in the Actions column of the instance and follow the on-screen instruction to complete the refund.

References

  • For information about the billing of ApsaraMQ for RocketMQ Enterprise Platinum Edition instances, see Billing.

  • For information about how to change the edition of an ApsaraMQ for RocketMQ Enterprise Platinum Edition instance, see Change the edition of an instance.