redis-cli
This section describes how to use redis-cli on an ECS in the same VPC as a DCS Redis instance to connect to the instance. For details about more clients, see the Redis official website.
- For Redis 4.0/5.0/6.0, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.
- When connecting to a Redis Cluster instance, ensure that -c is added to the command. Otherwise, the connection will fail.
- Run the following command to connect to a Redis Cluster instance:
./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c
- Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:
For details, see the procedure in this section.
- Run the following command to connect to a Redis Cluster instance:
Prerequisites
- A DCS Redis instance has been created and is in the Running state.
- An ECS has been created. For details about how to create an ECS, see Purchasing an ECS.
- If the ECS runs the Linux OS, ensure that the GCC compilation environment has been installed on the ECS.
Procedure (Linux)
- View the IP address/domain name and port number of the DCS Redis instance to be accessed.
For details, see Viewing Instance Details.
- Install redis-cli.
The following steps assume that your client is installed on the Linux OS.
- Log in to the ECS.
- Run the following command to download the source code package of your Redis client from https://download.redis.io/releases/redis-6.2.13.tar.gz:
wget http://download.redis.io/releases/redis-6.2.13.tar.gz
The following uses redis-6.2.13 as an example. For details, see the Redis official website.
- Run the following command to decompress the source code package of your Redis client:
- Run the following commands to go to the Redis directory and compile the source code of your Redis client:
make
cd src
If the source code of your Redis client is v6.0 and later, and redis-cli that supports TLS/SSL is required, replace the make command with make BUILD_TLS=yes to enable TLS.
- Access the DCS Redis instance.
- Access a DCS instance of a type other than Redis Cluster.
Perform the following procedure to access a single-node, master/standby, read/write splitting, or Proxy Cluster instance.
- Run the following command to access the chosen DCS Redis instance:
./redis-cli -h {dcs_instance_address} -p 6379
{dcs_instance_address} indicates the IP address/domain name of the DCS instance and 6379 is the port used for accessing the instance. The IP address/domain name and port number are obtained in 1.
For a Proxy Cluster DCS Redis instance, you can use the Connection Address or IP Address for {dcs_instance_address}. The addresses can be obtained on the instance basic information page on the console, as shown in Figure 1.
- Connection Address and IP Address are the LB addresses. Requests are distributed across proxy nodes.
The following example uses the domain name address of a DCS Redis instance. Change the domain name and port as required.
[root@ecs-redis redis-6.2.13]# cd src [root@ecs-redis src]# ./redis-cli -h redis-069949a-dcs-lxy.dcs.huaweicloud.com -p 6379 redis-069949a-dcs-lxy.dcs.huaweicloud.com:6379>
- If you have set a password for the DCS instance, enter the password in this step. You can read and write cached data only after the password is verified. Skip this step if the instance is not password-protected.
{password} indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
The command output is as follows:
redis-069949a-dcs-lxy.dcs.huaweicloud.com:6379> auth ******* OK redis-069949a-dcs-lxy.dcs.huaweicloud.com:6379>
- Run the following command to access the chosen DCS Redis instance:
- Access a DCS instance of the Redis Cluster type.
Perform the following procedure to access a Redis Cluster instance.
- Run the following command to access the chosen DCS Redis instance:
./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c
{dcs_instance_address} indicates the IP address/domain name of the DCS Redis instance, 6379 is the port used for accessing the instance, {password} is the password of the instance, and -c is used for accessing Redis Cluster nodes. The IP address/domain name and port number are obtained in 1.
- You can set {dcs_instance_address} to Connection Address or IP Address in the Connection section, or IP Address in the Instance Topology section. The addresses can be obtained on the instance basic information page on the console, as shown in Figure 2.
- If password-free access has been enabled for the instance, you do not need to enter the instance access password -a {password}. If you forget the password or need to reset the password, see Resetting Instance Passwords.
- The IP Address field provides multiple IP addresses. You can use any of them to connect to the instance. The CRC16(key) mod 16384 algorithm is used to compute what is the hash slot of a given key. For higher reliability, configure all IP addresses.
- By using the IP Address in the Instance Topology section, you can connect to the specified shard.
- The following example uses the IP address of a DCS Redis instance. Change the IP address and port as required.
root@ecs-redis:~/redis-6.2.13/src# ./redis-cli -h 192.168.0.85 -p 6379 -a ****** -c 192.168.0.85:6379>
- The following example uses the domain name of a DCS Redis instance. Change the domain name and port as required.
root@ecs-redis:~/redis-6.2.13/src# ./redis-cli -h redis-51e463c-dcs-lxy.dcs.huaweicloud.com -p 6379 -a ****** -c redis-51e463c-dcs-lxy.dcs.huaweicloud.com:6379>
- Run the following command to view the Redis Cluster node information:
Each shard in a Redis Cluster has a master and a replica by default. The proceeding command provides all the information of cluster nodes.
192.168.0.85:6379> cluster nodes 0988ae8fd3686074c9afdcce73d7878c81a33ddc 192.168.0.231:6379@16379 slave f0141816260ca5029c56333095f015c7a058f113 0 1568084030 000 3 connected 1a32d809c0b743bd83b5e1c277d5d201d0140b75 192.168.0.85:6379@16379 myself,master - 0 1568084030000 2 connected 5461-10922 c8ad7af9a12cce3c8e416fb67bd6ec9207f0082d 192.168.0.130:6379@16379 slave 1a32d809c0b743bd83b5e1c277d5d201d0140b75 0 1568084031 000 2 connected 7ca218299c254b5da939f8e60a940ac8171adc27 192.168.0.22:6379@16379 master - 0 1568084030000 1 connected 0-5460 f0141816260ca5029c56333095f015c7a058f113 192.168.0.170:6379@16379 master - 0 1568084031992 3 connected 10923-16383 19b1a400815396c6223963b013ec934a657bdc52 192.168.0.161:6379@16379 slave 7ca218299c254b5da939f8e60a940ac8171adc27 0 1568084031 000 1 connected
Write operations can only be performed on master nodes. The CRC16(key) mod 16384 algorithm is used to compute what is the hash slot of a given key.
As shown in the following, the value of CRC16 (KEY) mode 16384 determines the hash slot that a given key is located at and redirects the client to the node where the hash slot is located at.
192.168.0.170:6379> set hello world -> Redirected to slot [866] located at 192.168.0.22:6379 OK 192.168.0.22:6379> set happy day OK 192.168.0.22:6379> set abc 123 -> Redirected to slot [7638] located at 192.168.0.85:6379 OK 192.168.0.85:6379> get hello -> Redirected to slot [866] located at 192.168.0.22:6379 "world" 192.168.0.22:6379> get abc -> Redirected to slot [7638] located at 192.168.0.85:6379 "123" 192.168.0.85:6379>
- Run the following command to access the chosen DCS Redis instance:
- Access a DCS instance of a type other than Redis Cluster.
Procedure (Windows)
Click here to download the Redis client installation package for Windows. Decompress the package in any directory, open the CLI tool cmd.exe, and go to the directory. Then, run the following command to access the DCS Redis instance:
redis-cli.exe -h XXX -p 6379
XXX indicates the IP address/domain name of the DCS instance and 6379 is an example port number used for accessing the DCS instance. For details about how to obtain the IP address/domain name and port number, see Viewing Instance Details.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.