Cannot Connect to Redis-compatible YEDIS API

First, ensure that the expected YugabyteDB processes on the current node.At a minimum, the tserver process needs to be running to be able to connect to this node with a Redis client or application.Additionally, depending on the setup, you might expect a master process to also be running on this node.Follow the instructions on the Check Processes page.

If the tserver process is running, make sure the the YEDIS service is enabled and listening on the Redis port (default ).

When running a local cluster with yb-ctl you should see all the nodes here with different IPs. For instance:

If there is another process using this port you might need to stop that and restart the tserver process.Otherwise, if no process is listening but the tserver is running, check the value of the —redis_proxy_bind_address flag passed to thetserver process.

where <yb-local-address> is the address where the YEDIS service is listening (e.g. as returned by lsof). For instance, in the example above, it is localhost (or, additionally, 127.0.0.2 and for the yb-ctl case).

If redis-cli can connect, the issue is likely a network issue with the original client not being able to access this node where YugabyteDB is running. See also below.Otherwise, you might need to run ./yb-admin —master_addresses <master-ip-addresses> setup_redis_table". You can find the yb-admin tool in the Yugabyte directory.