ApsaraMQ for Kafka:Manage instance lifecycle

The Actions column for an ApsaraMQ for Kafka instance displays operations based on the instance state:

• If an operation is not displayed, it is unavailable.

• If an operation is grayed out, it is unavailable for the instance's current state.

• If an operation is highlighted, it is available.

Expiration (2 → 3): For an instance in the running state:

• If a subscription instance expires and you do not renew it in time, its state changes from running to expired.

• If you need to unsubscribe from a subscription ApsaraMQ for Kafka instance due to special circumstances, submit a ticket. After your request is approved, the instance state changes from running to expired.

Release (3 → 4 → 5):

• Manual release: To immediately release an expired instance, forcibly delete it in the console. The system schedules an asynchronous release task that starts as soon as the instance enters the expired state. After release, the instance is automatically deleted. You can view the task on the Tasks Pending for Scheduling tab of the instance details page.

• Automatic release: An instance in the expired state is automatically released after seven days. Its state then changes to released. After the instance is released, you can delete it from the console.

Stop or expiration (2 → 3): For an instance in the running state:

• If you no longer need the instance, you can stop it in the console. After the instance is stopped, its state changes from running to stopped.

  Warning

  You do not need to delete topics, groups, or other components before you stop an instance. Stopping an instance interrupts its services. Ensure your workloads are stopped before you proceed.

• If a pay-as-you-go instance has an overdue payment, its state changes from running to expired.

Release (3 → 4 → 5):

• Manual release: To immediately release a stopped or expired instance, forcibly delete it in the console. The system schedules an asynchronous release task that starts as soon as the instance enters the stopped or expired state. After release and final billing, the instance is automatically deleted. You can view the task on the Tasks Pending for Scheduling tab of the instance details page.

  Warning

  A forcibly deleted instance cannot be recovered. Do not add funds to your account during the forced deletion process. Otherwise, your payment may succeed, but the instance still cannot be recovered.

• Automatic release:

  • An instance in the stopped state is automatically released at 08:00 two days after it enters this state. Its state then changes to released. After the instance is released, you can delete it from the console.

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

  • An instance in the expired state due to an overdue payment is automatically released after seven days. Its state then changes to released. After the instance is released, you can delete it from the console.

Restoration (3 → 2):

• Enable: To resume using an instance in the stopped state, you can enable it in the console before it is automatically released at 08:00 two days after being stopped. Once enabled, the instance returns to the running state. If you do not enable the instance within this period, it is released and cannot be recovered.

• Add funds: To resume using an instance that is expired due to an overdue payment, you must add funds to your account within seven days. After the payment is successful, the instance returns to the running state. If you do not add funds within this period, the instance is released and cannot be recovered.