Alauda Cache Service for Redis OSS

Start & Stop Instance

Alauda Cache Service for Redis OSS provides one-click start and stop functionality to support operational flexibility in managing middleware instances. This capability is particularly valuable for temporarily releasing resources without deleting instances during maintenance windows, high node load scenarios, or in development/testing environments. Efficiently managing instance state helps optimize resource utilization and reduce operational costs.

TOC

Stop Instance

Stopping a Redis instance gracefully suspends its operation while preserving configuration and persistent data.

Prerequisites

The instance must be in one of the following states: Processing, Running, Abnormal, or Unknown.

Procedure

Web Console

Recommendation: Perform a complete backup before stopping an instance to safeguard against potential data loss.

  1. In the left navigation bar, click Redis.

  2. Click on namespace name.

  3. Click on instance name.

  4. Click Actions > Stop, and confirm the operation.

Features Unavailable During Stopped State

FeatureLimitation
Terminal ConsoleTerminal access to Redis instances is unavailable.
ActionsInstance operations including restart, update, and scheduling configuration changes are disabled.
TopologyTopology visualization is unavailable as the instance components are not running.
Parameter ConfigurationParameter updates and configuration exports cannot be performed.
User ManagementUser administration functionality is inaccessible.
Backup & RestoreNew backup operations cannot be initiated.
InspectionInspection metrics and results for the stopped instance are invalid.
Access MethodRouting information may be unavailable or inaccessible.

Start Instance

Starting a previously stopped Redis instance restores full functionality and service availability.

Prerequisites

The instance must be in Stopping or Stopped state.

Procedure

Web Console

  1. In the left navigation bar, click Redis.

  2. Click on namespace name.

  3. Click on instance name.

  4. Click Actions > Start, and confirm the operation.

After the start operation completes successfully, the instance transitions to the Running state and all features become available again.