Redis upgrades break working setups

Outages and change2 posts from 2 people2d active+11 post in the last 7 days, 0 the 7 days before (steady)Unverified

Posts per day2 posts, Aug 29 to Sep 28

The posts behind it

2, newest first

Post	Where	Date
[Bug]: DualCache writes Redis entries with `default_in_memory_ttl`, so a configured `default_redis_ttl` never takes effect### Description `DualCache` accepts a Redis TTL in three places and never reads it back. `self.default_redis_ttl` is assigned at `litellm/caching/dual_cache.py:77` (constructor), `:84` (`update_cache_ttl`) and `:106` (`attach_redis_cache`), and there is no read of it anywhere in...BerriAI/litellmlets-order-some-fries	BerriAI/litellmlets-order-some-fries	Sep 253 days ago
Explicit falsy Redis client overrides should not fall back to settings...`0` values for `port`, `db`, and `health_check_interval`. ### Reproduction This makes it impossible to explicitly disable TLS for a local/test client while inheriting a shared settings object, and it also prevents callers from selecting database 0 when settings select another...PrefectHQ/prefectqdivan	PrefectHQ/prefectqdivan	Aug 294 weeks ago

Companies and products named

Company or product	Posts naming it
Redis	2
Prefect	1

About this problem

Evidence

2 posts from 2 people in 2 places, about 1 a week over 28 days. Mostly on PrefectHQ/prefect, BerriAI/litellm. Tools named alongside: Prefect.

Frustration Frustration 3 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "breaking-changes" rule about Redis. First post Aug 29, 2026, latest Sep 25, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere

Posts per day

The posts behind it

Companies and products named

Rising problems by email