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.0.684
Environment (OS name and version): Windows 7
Redis Server Version: 4.0.1
Steps to reproduce:
Configure a connection with the parameters for one of the nodes in the cluster. Enter the respective hostname and port.
Try "Test Connection" - working fine.
Try to connect. Connection is established and correctly showing only "db0".
Attempt to open "db0" rdm starts the scanning and at some point the connection is dropped. Eventually getting a message "Cannot connect to cluster node xxx.xxx.xxx.xxx:0". Not that the hostname is rewritten with IP Address but the port is rewritten with 0.
Correction the 0 to 6379 for instance for the port would result in the ability to try to connect again until we get the same message for another node. The port value is usually overwritten mostly with 0 and sometimes with 1.
Expected result:
Successfully connection to the cluster and being able to see the data.
Actual Result:
Not being able to see any data, connection parameters overwritten and seeing error messages due to that.
The text was updated successfully, but these errors were encountered:
RDM Version: 0.9.0.684
Environment (OS name and version): Windows 7
Redis Server Version: 4.0.1
Steps to reproduce:
Configure a connection with the parameters for one of the nodes in the cluster. Enter the respective hostname and port.
Try "Test Connection" - working fine.
Try to connect. Connection is established and correctly showing only "db0".
Attempt to open "db0" rdm starts the scanning and at some point the connection is dropped. Eventually getting a message "Cannot connect to cluster node xxx.xxx.xxx.xxx:0". Not that the hostname is rewritten with IP Address but the port is rewritten with 0.
Correction the 0 to 6379 for instance for the port would result in the ability to try to connect again until we get the same message for another node. The port value is usually overwritten mostly with 0 and sometimes with 1.
Expected result:
Successfully connection to the cluster and being able to see the data.
Actual Result:
Not being able to see any data, connection parameters overwritten and seeing error messages due to that.
The text was updated successfully, but these errors were encountered: