redis-py ft.dropindex() crashes server (Fix)

The Fix

pip install redis==7.1.0

Based on closed redis/redis-py issue #2265 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -20,6 +20,7 @@
 ADDHASH_CMD = "FT.ADDHASH"
 DROP_CMD = "FT.DROP"
+DROPINDEX_CMD = "FT.DROPINDEX"
 EXPLAIN_CMD = "FT.EXPLAIN"
 EXPLAINCLI_CMD = "FT.EXPLAINCLI"

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.\n\n

Why This Fix Works in Production

Trigger: ft.dropindex() crashes server
Mechanism: Changes the `dropindex()` method to use the `FT.DROPINDEX` command instead of the `FT.DROP` command, preventing server crashes when the index is not present.
Why the fix works: Changes the `dropindex()` method to use the `FT.DROPINDEX` command instead of the `FT.DROP` command, preventing server crashes when the index is not present. (first fixed release: 7.1.0).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Production symptom (often without a traceback): ft.dropindex() crashes server

Proof / Evidence

GitHub issue: #2265
Fix PR: https://github.com/redis/redis-py/pull/2315
First fixed release: 7.1.0
Reproduced locally: No (not executed)
Last verified: 2026-02-07
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.71

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“In the past FT.DROP was the drop command (here's a historic link): https://d128ysc22mu7qe.cloudfront.net/Commands/#ftdrop”

@chayim · 2022-07-21 · source

“Grrr apparently I can't label today? @dvora-h can you mark "bug" and "breakingchange"”

@chayim · 2022-07-21 · source

Failure Signature (Search String)

ft.dropindex() crashes server
Hello, I'm using version `4.3.4` and found out that `dropindex()` crashes the server when the index is not present. [Related

Copy-friendly signature

signature.txt

Failure Signature
-----------------
ft.dropindex() crashes server
Hello, I'm using version `4.3.4` and found out that `dropindex()` crashes the server when the index is not present. [Related to](https://github.com/RediSearch/RediSearch/issues/2152)

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
ft.dropindex() crashes server
Hello, I'm using version `4.3.4` and found out that `dropindex()` crashes the server when the index is not present. [Related to](https://github.com/RediSearch/RediSearch/issues/2152)

What Broke

The server crashes when attempting to drop a non-existent index.

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install redis==7.1.0

When NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/redis/redis-py/pull/2315

First fixed release: 7.1.0

Last verified: 2026-02-07. Validate in your environment.

When NOT to Use This Fix

Do not use if it changes public behavior or if the failure cannot be reproduced.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
7.1.0	Fixed

Related Issues

No related fixes found.

Cluster: redis-py:configuration-error redis-py hub redis-py best practices All hubs All clusters

Related clusters: Retry storm Data consistency Race condition

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.