Description
The official go-redis client exposes a ClusterClient which is exposed via NewClusterClient. However, this tracing library only exposes the UniversalClient:
This is problematic, as the implementation of the UniversalClient is entirely dependent on the length of addresses sent under the Addrs
key of UniversalClient
:
However, when using AWS ElastiCache for Redis, their implementation only exposes a single "configuration endpoint":
Once your cluster is “available,” it is ready for use. You can connect to the cluster using the Configuration Endpoint listed in the AWS Management Console.
This single address is used to connect into the cluster. Therefore, the go-redis UniversalClient will assume single-node mode, and fail to connect to the cluster. Therefore, when using AWS ElastiCache for Redis and go-redis, the ClusterClient must be manually specified.
Therefore, this request is to expose ClusterClient in this tracing pacakge.