database · inferred from evidence
Redis
An in-memory data structure store used as a database, cache, and message broker.
- RedisVL: documents not immediately searchable after load on Redis 8.8+
This is server behavior, not a redisvl defect: on Redis 8.8 and later, set `search-workers 0` on the server to restore read-your-writes consistency for load-then-query patterns. With the default multithreaded background executor, queries is
- Prefect 3 server memory grows until OOM with default in-memory messaging
The Prefect 3 server leak came from the in-memory event messaging path used when no Redis is configured: unbounded internal queues plus a fakeredis Lua-runtime leak under the default `memory://` Docket broker. Fix: upgrade Prefect to 3.6.16
- Lago events ingested but events_count stays 0 in current usage API
The events are being counted; the usage endpoint serves a cached value that isn't invalidated at ingestion time. The fix that worked for reporters: clear the Redis cache, or simply call the current_usage endpoint again — it refreshes its ca