Prerequisites for using Cloud DB for Redis
- Print
- PDF
Prerequisites for using Cloud DB for Redis
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
View supported environments, server specifications, and restrictions, etc. for smooth use of Cloud DB for Redis.
Cloud environment specifications
The following details are about the cloud environment specifications supported by Cloud DB for Redis.
| Items | Supported specifications |
|---|---|
| Region (zone) | Korea, United States, Singapore, Japan, and Germany |
| Classic | Supported |
| VPC | Supported |
| Language | Korean, English, and Japanese |
Note
Please refer to Service introduction in NAVER Cloud Platform portal if you would like to know more about the VPC environment, and to Ncloud use environment guide if you would like to know whether a VPC environment is supported for individual services.
Server specifications
For NAVER Cloud Platform's Cloud DB for Redis, you can flexibly select from various types of server type and use them according to your service size. For server specifications supported by Cloud DB for Redis, refer to Service > Database > Redis in the portal.
Caution
A maximum of 10 high memory type servers can be created per user account, and a maximum of 20 servers can be created per account, regardless of type. If you need to create servers in quantities over the limit, then please contact Support.
Restrictions when changing server specifications
While the type of Redis server that has been created and is in operation can't be changed, the size of available memory can always be changed using the Change specifications feature of the Redis server menu in the console. For the upgrade method, please refer to Redis server. However, a few restrictions exist when changing the server specifications. You need to fully understand these restrictions before changing the server specifications. The restrictions are as follows.
- They can only be changed within the same type.
- They can only be changed to a larger cache memory size type due to the in-memory characteristics.
- If configured with 2 servers: Active and standby (using high availability) will both be changed to the same specifications.
- The server restarts upon completion of change. Therefore, the service may possibly be affected.
The data continuity is guaranteed as the data in memory is saved to a disk when the server specifications are changed. However, when the change of server specifications is completed, we recommend checking the data status using the dbsize command.
Server redundancy configuration
Cloud DB for Redis supports the high availability (HA) feature. When an error occurs in the active server and normal service is unavailable, it performs automatic failover to the standby server. Since the redundancy is configured in the DNS method, no additional application change is required. When creating the Redis server from the NAVER Cloud Platform console, you can select whether to use high availability (HA). The server configuration will then change according to the use status. The following describes the server configuration by use status.
| Use of high availability | Number of created servers (units) | Configuration |
|---|---|---|
| O | 2 | Active Master, Standby Master |
| X | 1 | Standalone |
Caution
When performing failover, it may take up to 3 minutes.
Redis command restrictions
For smooth service operation of Cloud DB for Redis, certain Redis commands can't be used. The following are commands that are unavailable for use.
BGREWIRTEAOFBGSAVESAVESLAVEOFFLUSHALLFLUSHDBCONFIGKEYSMIGRATESHUTDOWN
Caution
To supplement the role of unavailable Redis commands, APIs are supported. For the usage method for APIs of Cloud DB for Redis, please refer to Cloud DB for Redis (VPC) API guide.
Usage fees
Cloud DB for Redis is serviced on a pay-as-you-go pricing plan. For details about the Cloud DB for Redis's pricing standard, refer to the Portal > Service > Database > Cloud DB for Redis menu or the Portal > Pricing menu.
Was this article helpful?