[Feature Request]: Retain cluster hostname, so that when IP addresses change we don't need to update the connection
Nobody has claimed this yet.
- 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).
Currently any time we update an elasticache cluster, we can no longer connect in RedisInsight because it only retains node IP address(es).
How often do you encounter this problem (Describe how frequently this problem occurs).
Every time a cluster change happens resulting in new IP addresses of each cluster node
Alternatives considered (Describe any alternative features or products you've considered).
"Another Redis Desktop Manager" handles this fine... and so should the official redis tools.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies RedisInsight's cluster connection handling as the affected area, but names no files, tests, or entry points. Start by tracing how cluster node addresses are stored and reused after a cluster update; done means the cluster hostname is retained so RedisInsight reconnects when node IP addresses change, with coverage for that update scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, typescript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100