You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RDM Version: 0.9.1.771
Environment (OS name and version): Windows 10
Redis Server Version: 4.0.3 / Elasticache
Steps to reproduce:
Connect to clustered instance
I'm not sure what to expect. But what I see is several duplicated keys. This particular cluster has 6 members with 1 replica each (total of 12).
So for example when I load the keys I see this:
However when I use redis-cli I'm not getting all these duplicated results.
It would be really nice if when connecting to a cluster, it enumerated the masters and slaves of the cluster, and then provided the option to scan the keyspace on a specific server.
As it stands using this on Clustered instances isnt working very well.
The text was updated successfully, but these errors were encountered:
- Add support for ECDSA host key to connect to Elastic Cache (#4047)
- Clone connection to prevent modification of connection settings (#4078)
- Fix cluster keys retrival (#4058 and #4117)
- Add support for ECDSA host key to connect to Elastic Cache (#4047)
- Clone connection to prevent modification of connection settings (#4078)
- Fix cluster keys retrival (#4058 and #4117)
RDM Version: 0.9.1.771
Environment (OS name and version): Windows 10
Redis Server Version: 4.0.3 / Elasticache
Steps to reproduce:
I'm not sure what to expect. But what I see is several duplicated keys. This particular cluster has 6 members with 1 replica each (total of 12).
So for example when I load the keys I see this:
However when I use redis-cli I'm not getting all these duplicated results.
It would be really nice if when connecting to a cluster, it enumerated the masters and slaves of the cluster, and then provided the option to scan the keyspace on a specific server.
As it stands using this on Clustered instances isnt working very well.
The text was updated successfully, but these errors were encountered: