redis / redis/RedisInsight

[Feature Request]: Specifying multiple hosts for single cluster entry

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

Nobody has claimed this yet.

feature status: accepted
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).

When having redis cluster I'd like to still be able to connect to the cluster from Redis Insighteven if one of the nodes is down. Currently if the host which is specified is down then whole cluster is not reachable from Redis Insight.

How often do you encounter this problem (Describe how frequently this problem occurs).
Twice a year for a week.

Alternatives considered (Describe any alternative features or products you've considered).

Adding each host separately but it's a lot of additional work for a lot of redises and enlarges list of redises enormously.

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

Could be related to https://github.com/redis/RedisInsight/issues/2809 as it is in area of enhancing redis cluster support. Also https://github.com/redis/RedisInsight/issues/3035 is somehow connected because slaves are missing from the list. If somebody wanted to enhance cluster support overall such trio is quite nice.

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 reviewing the related issues 2809 and 3035, then inspect the existing Redis cluster connection handling. Done means one cluster entry can specify multiple hosts and Redis Insight remains reachable when one node is down, without requiring separate entries for every host.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
databases, distributed-systems
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.