Closed sureshvasanthkumar closed 2 weeks ago
Please let me check into the issue and get back to you.
This is a similar issue on other Redis clients. So far it seems to have been fixed on lettuce. It will soon be fixed on redis-cli - https://github.com/redis/redis/issues/12266
This issue is marked stale. It will be closed in 30 days if it is not updated.
Version: 4.5.5
Platform:
Ubuntu 20.04 Python 3.10.6 pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10) Redis cluster - redis-server version 7.0.11, All redis cluster member instances are accessible via the same hostname/IP address but on different ports.
Description:
When the Redis cluster is configured with
cluster-preferred-endpoint-type unknown-endpoint
, it indicates that the server doesn't know how clients can reach it during redirects. This is made clear to the client from the null/None response on the host field during redirects from the server. In this case, the server is expecting the client to reach out on the same endpoint it used for making the last request, but use the new port provided in the response.This does not happen with redis-py. It tries to connect with the null/None hostname during redirects which is not the expected behavior from the server. This results in the following traceback.
Expected behavior:
When a server redirects a client with
:new port
, the client should connect using the same hostname/IP/endpoint it used previously to connect to the server but with thenew port
value indicated in the redirect.