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
Currently, In the case there are multiply client connections on master node, there are several replica nodes and sentinel connected to the master node.
When client run "info" command, client could see the client connection number, replica node infomation, but no sentinel node infomation provided. Client can only logon the sentinel node client and see the sentinel infomation.
Description of the feature
Client wish to see the sentinel infomation on the master node information.
The text was updated successfully, but these errors were encountered:
Hi @hwware,
Unless you have any idea how to implement it clean and easy, i doubt if it worth the effort.
Redis nodes are totally unaware of sentinel existence (even though they share same codebase).
Current state of sentinel is distributed/duplicated among sentinel instances.
And from what I know, there is no any future plans for Sentinel.
The problem/use-case that the feature addresses
Currently, In the case there are multiply client connections on master node, there are several replica nodes and sentinel connected to the master node.
When client run "info" command, client could see the client connection number, replica node infomation, but no sentinel node infomation provided. Client can only logon the sentinel node client and see the sentinel infomation.
Description of the feature
Client wish to see the sentinel infomation on the master node information.
The text was updated successfully, but these errors were encountered: