redis / redis/RedisInsight

[Feature Request]: Cluster - random selection of endpoints to execute command against

Open
#2,809 6 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
TypeScript
Stars
8.8k
Forks
491
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Problem description (Describe the problem you would like to solve with this feature request or suggested idea).
I can't execute targeted commands for selected nodes. CLI for database opens connected to only one of the endpoints.
It would be great to have possibility to execute commands in CLI or workbench:

  • on any endpoint
  • on selected endpoint in cluster (let's say dropdown with masters and replicas with smaller font info if it's master/replica)
  • in cluster mode or not (like -c in redis-cli)

This would greatly help to enhance RedisInsight also as a tool for general redis management on lower level.

How often do you encounter this problem (Describe how frequently this problem occurs).
From time to time during analysing issues with redis libraries.

Alternatives considered (Describe any alternative features or products you've considered).
Adding every endpoint as separate redis database but even though I put for example ip 10.0.0.1 in host field it still gets changed automatically after saving database to some other endpoint.

Additional information (Add any other context or details here).

I'm using v 2.34.0 running on k8s

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing endpoint selection and command execution in the RedisInsight CLI and workbench, including how cluster mode is handled. The feature is complete when commands can target any endpoint, a selected master or replica, or the cluster as a whole, with endpoint roles visible to the user.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
cli, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.