Skip Menu |

This queue is for tickets about the Redis-Cluster CPAN distribution.

Report information
The Basics
Id: 119851
Status: new
Priority: 0/
Queue: Redis-Cluster
People
Owner: Nobody in particular
Requestors: pupton [...] twst.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Jan 13 16:55:32 2017 pupton [...] twst.com - Ticket created
Subject: Can not connect
Date: Fri, 13 Jan 2017 14:54:33 -0700
To: bug-Redis-Cluster [...] rt.cpan.org
From: Phillip Upton <pupton [...] twst.com>
When using Redis::Cluster (0.14) running the code in the synopsis I get the following error: Could not connect to Redis server at 127.0.0.1:7000:3d2e4c5a8c1b07f9af660ac9cb77831a525ddee9: at /home/twst/scripts/../Incentive/lib/Redis/Cluster.pm line 667. The documentation for the ‘cluster slots’ command at https://redis.io/commands/cluster-slots has the following warning: Newer versions of Redis Cluster will output, for each Redis instance, not just the IP and port, but also the node ID as third element of the array. In future versions there could be more elements describing the node better. In general a client implementation should just rely on the fact that certain parameters are at fixed positions as specified, but more parameters may follow and should be ignored. Similarly a client library should try if possible to cope with the fact that older versions may just have the IP and port parameter. The attached patch fixes the problem. Thanks, —Phillip Upton
When using Redis::Cluster (0.14) running the code in the synopsis I get the following error:

Could not connect to Redis server at 127.0.0.1:7000:3d2e4c5a8c1b07f9af660ac9cb77831a525ddee9:  at /home/twst/scripts/../Incentive/lib/Redis/Cluster.pm line 667.

The documentation for the ‘cluster slots’ command at https://redis.io/commands/cluster-slots has the following warning:

Newer versions of Redis Cluster will output, for each Redis instance, not just the IP and port, but also the node ID as third element of the array. In future versions there could be more elements describing the node better. In general a client implementation should just rely on the fact that certain parameters are at fixed positions as specified, but more parameters may follow and should be ignored. Similarly a client library should try if possible to cope with the fact that older versions may just have the IP and port parameter.

The attached patch fixes the problem.

Thanks,

—Phillip Upton

Message body is not shown because sender requested not to inline it.