ApsaraMQ for Kafka:Manage the lifecycle of an instance

The manner in which an operation is displayed in the Actions column of an ApsaraMQ for Kafka instance determines whether the operation can be performed.

• If an operation is not displayed, you cannot perform the operation.

• If an operation is grayed out, you cannot perform the operation in the current instance status.

• If an operation is highlighted, you can perform the operation.

Expiration (2 → 3): The following items describe how the status changes after an instance that is in the Running state expires:

• If the instance is not renewed within the required period of time, the status of the instance changes from Running to Expired.

• If you want to unsubscribe from an ApsaraMQ for Kafka instance, submit a ticket. After the instance is unsubscribed, the status of the instance changes from Running to Expired.

Release (3 → 4 → 5):

• Proactive release: If you want to immediately release an instance after it expires, you can forcibly delete the instance in the ApsaraMQ for Kafka console. After you perform the force deletion operation, the system schedules an asynchronous task to delete the instance. When the system detects that the status of the instance becomes Expired, the system immediately releases and deletes the instance. You can view the scheduled task on the Tasks Pending for Scheduling tab of the Instance Details page.

• Passive release: If you do not renew an instance, the instance is automatically released seven days after it enters the Expired state. After the instance is released, the status of the instance changes to Released. You can delete the released instance in the ApsaraMQ for Kafka console.

Stopping or expiration (2 → 3): The following items describe how the status changes after an instance in the Running state is stopped or expires:

• If you stop the instance in the ApsaraMQ for Kafka console, the status of the instance changes from Running to Stopped.

  Warning

  Before you stop an instance, you do not need to delete the topics, groups, or components on the instance. However, you must stop your business because services are interrupted after you stop the instance.

• If the instance is stopped due to insufficient account balance, the status of the instance changes from Running to Expired.

Release (3 → 4 → 5):

• Proactive release: If you want to immediately release an instance after it stops or expires, you can forcibly delete the instance in the ApsaraMQ for Kafka console. After you perform the force deletion operation, the system schedules an asynchronous task to delete the instance. When the system detects that the status of the instance becomes Stopped or Expired, the system immediately releases the instance. After the bill is generated, the instance is automatically deleted. You can view scheduled tasks on the Tasks Pending for Scheduling tab of the Instance Details page.

  Warning

  You cannot restore an instance that you forcibly deleted. Do not add funds to your account when an instance is being forcibly deleted. Otherwise, the funds may be added, but you cannot restore the instance.

• Passive release:

  • An instance is automatically released at 8:00 two days after it enters the Stopped state. After the instance is released, the status of the instance changes to Released. You can delete the released instance in the ApsaraMQ for Kafka console.

    For example, if an instance is stopped at 14:00 on October 13, 2023, the instance is automatically released at 8:00 on October 15, 2023.

  • An instance is automatically released seven days after it enters the Expired state. After the instance is released, the status of the instance changes to Released. You can delete the expired instance in the ApsaraMQ for Kafka console.

Restoration (3 → 2):

• Enable: If you want to use an instance that is in the Stopped state, you can log on to the ApsaraMQ for Kafka console to enable the instance before it is released at 8:00 on the third day after it enters the Stopped state. After the instance is enabled, the status of the instance becomes Running. If you do not enable the instance before the required period of time, the instance is released. A released instance cannot be restored.

• Add funds: If you want to use an instance that is in the Expired state, you can add funds to your account in the ApsaraMQ for Kafka console within seven days after the instance expires. After sufficient funds are added to your account, the status of the instance changes to Running. If you do not add sufficient funds to your account within the required period of time, the instance is released. You cannot restore a released instance.