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.
Stopping a Redis instance gracefully suspends its operation while preserving configuration and persistent data.
The instance must be in one of the following states: Processing, Running, Abnormal, or Unknown.
Recommendation: Perform a complete backup before stopping an instance to safeguard against potential data loss.
In the left navigation bar, click Redis.
Click on namespace name.
Click on instance name.
Click Actions > Stop, and confirm the operation.
Feature | Limitation |
---|---|
Terminal Console | Terminal access to Redis instances is unavailable. |
Actions | Instance operations including restart, update, and scheduling configuration changes are disabled. |
Topology | Topology visualization is unavailable as the instance components are not running. |
Parameter Configuration | Parameter updates and configuration exports cannot be performed. |
User Management | User administration functionality is inaccessible. |
Backup & Restore | New backup operations cannot be initiated. |
Inspection | Inspection metrics and results for the stopped instance are invalid. |
Access Method | Routing information may be unavailable or inaccessible. |
Starting a previously stopped Redis instance restores full functionality and service availability.
The instance must be in Stopping or Stopped state.
In the left navigation bar, click Redis.
Click on namespace name.
Click on instance name.
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.