communication config_error ai_generated true

Session affinity lost: request routed to different backend

ID: communication/load-balancer-session-affinity

Also available as: JSON · Markdown
78%Fix Rate
82%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
any active — — —

Root Cause

Load balancer lost session affinity, routing to wrong backend.

generic

Workarounds

  1. 88% success Use cookie-based session affinity
  2. 92% success Move session state to shared store (Redis) to eliminate affinity need

Dead Ends

Common approaches that don't work:

  1. Use IP-based affinity 75% fail

    Fails behind NAT/proxy, same IP for many users

  2. Disable load balancing 82% fail

    No redundancy