Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Cluster do not see slave nodes #3035

Open
jakub-kubera opened this issue Feb 9, 2024 · 4 comments
Open

[Bug]: Cluster do not see slave nodes #3035

jakub-kubera opened this issue Feb 9, 2024 · 4 comments

Comments

@jakub-kubera
Copy link

I have cluster with master nodes and slave nodes, replicas, but when I have added master nodes it showing only master nodes

@vajradhar
Copy link

Yes this feature was available in 1.x versions earlier but its no longer supported with new versions. Is there a roadmap to include this feature?

@ViktarStarastsenka
Copy link
Collaborator

currently, this feature is not prioritized for any upcoming releases
can you describe your use cases? why do you need to monitor replicas?

@jakub-kubera
Copy link
Author

I do not want to monitor replicas, but it would be good to know which replicas are in cluster, how many replicas are there, if slaves are in sync, possibility to failover if needed, resync keys, promote slave to master, move shards, make reshard, currently there is no any additional value/option with redisinsight, only checking cached key values

@Skoucail
Copy link

I totally agree, i used the failover feature in redisinsight v1 a lot. (fe when doing controlled rolling upgrades of the cluster)
And having a visual representation of the cluster with masters and replica's was a quick wat to see that everything was looking ok.

Also because Workbench/CLI doesn't have the feature to select the endpoint like we were able in v1. Its now almost impossible to trigger failovers with redis insight. (#2809)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants