Troubleshoot common issues

Available in Classic and VPC

You might run into the following problems when using Cloud DB for Cache: Find out causes and possible solutions.

DB Server connection error

Error occurs when connecting to DB Server.
Cannot access DB Server from outside.
Currently using SSL VPN but cannot connect to Cloud DB for Cache.

Cause

• You can't directly access the DB Server from outside.
• You need to create an application server that will communicate with DB Server to access DB Server. Otherwise, Cloud DB for Cache of NAVER Cloud Platform cannot be used normally.
• If execution of SSL VPN Agent is paused, you may not be able to access.

Solution

• DB Server created from Cloud DB for Cache is currently only accessible within NAVER Cloud Platform, so the applications server must also be created inside NAVER Cloud Platform. For the overall flow of server creation, check scenario and see Start guide by environment for each platform:
  • Overall usage quickstart
  • Getting started with Cloud DB for Cache (VPC)
  • Getting started with Cloud DB for Cache (Classic)
• Check if the SSL VPN Agent is in operation. If you can't access the DB even though Agent is running, see Set access environment in Getting started with Cloud DB for Cache.
• Check network settings for SSL VPN. You should set routing rules for SSL VPN IP Pool in the Route Table applied to VPC that will access SSL VPN. For more information, see network settings.

Notifications on exceeding DB Server threshold

Unable to receive an event notification on exceeding DB Server threshold.

Cause

Cloud DB for Cache provides monitoring service and event collection service for the performance and operating system of the server. You can directly set thresholds by integrating with Cloud Insight. If there's an error between Cloud Insight integrations and custom config value, notification may not be sent normally.

Solution

The monitoring results and event collection results of Cloud DB for Cache can be integrated with Cloud Insight to get notifications through email or SMS. For detailed usage, see below information by environment for each platform:

• VPC: Monitoring, Event
• Classic: Monitoring, Event

DB Cluster's server redundancy configuration (HA) and data sharding (VPC)

DB Cluster's server redundancy configuration (HA) and data sharding do not work properly.

Cause

DB Cluster's server redundancy configuration (HA) and data sharding are using native features of DB Cluster and if using client that is not incompatible, it may not work normally.

Solution

Check available clients from Connect with DB clients and use compatible clients.

Restore lost data

I want to restore lost data.

Cause

If failure occurs, cache data may be lost.

Solution

From Backup, click [Restore]. Based on backup data, you can create new DB cache server. For more information, see restoration.

Commands error

Key value lookup, key value initialization commands such as KEYS, FLUSH are not executed.

Cause

For service stability, some commands such as KEYS, FLUSH is limited.

Solution

Use SCAN commands instead of KEYS commands. You can execute the features related to FLUSH in the console. For unavailable commands from Cloud DB for Cache, see commands service limits.

Version upgrade

Feature for version upgrade not found.

Cause

There is no official major version upgrade.

Solution

Create new Cloud DB for Cache server and proceed with data migration. You can import key data using Dump feature in DB. For more information, see DUMP.

Add user

Unable to add user in Cloud DB for Cache.
I can see the feature to add user in Public platform but not in Private platform.

Cause

Private platforms do not support Add user accounts feature as ACL functionality does not apply to Cluster.
In Public cloud, you can add user accounts for CSAP authentication in Simple format, not Cluster.

Solution

The specification is that Add user feature is not supported in Private Platform. If ACL functionality to be applied in Cluster, you will be informed through portal or through guide.