Session: redis-cluster-failover — 2026-10-27

edge-cache · OpenCode · branch fix/redis-failover · gpt-5 · 2026-10-27 09:45 · 1 msgs · 4 tools · 1 min read · updated 9 days ago

tools: Bash, Edit, Write
← edge-cache Download .md .txt .json
Tool calls
Bash Bash: 2 calls (50.0%) 2 Edit Edit: 1 call (25.0%) 1 Write Write: 1 call (25.0%) 1
Token usage151.2K total
Input16.2K
Cache creation32.4K
Cache read97.2K
Output5.4K
Cache hit ratio67%· warming up

Project: edge-cache · Branch: fix/redis-failover · Mode: default · Model: gpt-5

Summary

Debugged cache misses spiking during Redis failovers: the client kept a stale slot map. Enabled RouteByLatency with MaxRedirects, added a circuit breaker that falls back to the in-memory LRU, and wrote a chaos test with toxiproxy.

Conversation

Turn 1 — User

Every Redis failover gives us a minute of 100% misses.

Turn 1 — Assistant

The client keeps routing to the demoted primary until the slot map refreshes. Refresh on MOVED, add a breaker that degrades to the local LRU, and reproduce with toxiproxy in CI.

Tools used in this turn:

  • Bash: docker compose -f chaos.yml up -d
  • Edit: store/redis.go
  • Write: store/breaker.go
  • Bash: go test ./chaos -run Failover — ok

Connections

  • [[edge-cache]]
  • [[Redis]]
  • [[CircuitBreaker]]
  • [[ChaosTesting]]

Keyboard shortcuts

⌘K / Ctrl+KOpen command palette
/Focus search
g hGo to home
g pGo to projects
g sGo to sessions
j / kNext / prev row (tables)
?Show this help
EscClose dialogs

Structured queries

Mix key:value filters with free text in the palette:

type:sessionOnly session pages
project:llm-wikiFilter by project name (substring)
model:claudeFilter by model name (substring)
date:>2026-03-01Sessions after a date
date:<2026-04-01Sessions before a date
tags:rustPages mentioning a tag/topic
sort:dateSort results by date (newest first)

Example: type:session project:llm-wiki date:>2026-04 sort:date