redis / redis/RedisInsight

[Bug]: Not all nodes are shown (2.52.0)

Open
#3,617 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Preconditions (Any important steps we need to know)
Redis cluster created on slurm.

Steps to reproduce (How to reproduce what you found step by step)

  1. Create cluster nodes
srun -l --nodes=1 --ntasks=1 -w $node redis-server --port ${PORT} --cluster-enabled yes --cluster-config-file ${REDIS_BASE}/node_${NODE_NUM}.conf --appendonly no --save "" --dir /example_folder --cluster-node-timeout 5000 --daemonize no &

redis-cli --cluster create $HOSTS --cluster-yes
  1. Connecting with cluster via SSH

Actual behavior (A short description of what you found)
In an earlier version of the Redis Insight everything was visible (e.g. 8 primary nodes). For now (ver. 2.52.0) I tested connection (which is unstable) with different numbers of nodes (new cluster every time, on different nodes). Every time got Primary nodes - 1 which is weird because CLI shows real number.

Expected behavior (A short description of what you expected to find)
Real number of primary nodes and their statistics.

Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)
Redis_bug_RI_2-52-0

Additional context (Operating system, version of Redis Insight, Redis database version, Redis module version, database type, connection type, logs, or any other information)
Slurm, Redis cluster based on Redis 7.0.8, Redis Insight 2.52.0

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 reproducing the Redis 7.0.8 cluster from the provided srun and redis-cli commands, then connect to it in Redis Insight 2.52.0 and compare the displayed primary-node count with the CLI result. Trace the cluster view and its node statistics until the missing node is accounted for; done means all primary nodes and their statistics are shown reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
database, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.