redis / redis/RedisInsight

[Bug]: Bulk delete completely broken with Redis Sentinel setup

Open
#4,806 3 comments 0 reactions 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 setup: 1 Master + 1 Slave + 2 Sentinels (NOT clustered)
  • RedisInsight connected via Sentinel configuration
  • Master name: myMaster
  • Individual key deletion works fine
  • Connection to Redis is stable and functional

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

  1. Connect RedisInsight to Redis using Sentinel configuration
  2. Navigate to Browser tab and view keys
  3. Select any number of keys (even just 1 key) using checkboxes or pattern selection
  4. Click "Bulk Actions" → "Delete Keys"
  5. Confirm deletion in the dialog
  6. Observe browser Network tab during this process

Actual behavior (A short description of what you found)

  • No keys are deleted regardless of selection size (1 key or 1000 keys)
  • Browser Network tab shows only socket.io polling requests
  • No DELETE API calls to /api/databases/.../keys endpoint are made
  • UI shows the delete dialog but no actual deletion occurs
  • Keys remain in Redis after "successful" bulk delete operation

Expected behavior (A short description of what you expected to find)

  • Selected keys should be deleted from Redis
  • Browser should show DELETE API requests to RedisInsight backend
  • Keys should disappear from the UI after successful deletion
  • Bulk delete should work the same way as individual key deletion

Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)
[A képernyőképet itt csatolnád a bulk delete dialog-ról és a Network tab-ról]

Additional context (Operating system, version of RedisInsight, Redis database version, Redis module version, database type, connection type, logs, or any other information)

  • Operating system: Kubernetes cluster (Linux containers)
  • RedisInsight version: 2.70
  • Redis database version: 8.0.2
  • Redis modules: None
  • Database type: Redis with Sentinel (cluster support disabled)
  • Connection type: Sentinel-based connection
  • No relevant error logs in RedisInsight or Redis
  • Workaround: Redis CLI bulk delete works perfectly
  • Issue exists regardless of key count or key type (Hash, String, etc.)

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

Reproduce the Sentinel connection flow in RedisInsight 2.70, then trace the Browser tab's Bulk Actions → Delete Keys path and compare it with individual key deletion. Check why no DELETE request reaches /api/databases/.../keys; done means selected keys are removed and disappear from the UI for Sentinel-backed databases.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.