Classic298 5586964bb2 fix: keep the usage pool cleanup task alive across lock loss and Redis errors (#28834) ...

With WEBSOCKET_MANAGER=redis on a multi-node deployment, the usage pool cleanup task could stop permanently for the whole cluster. Nodes that lost the startup lock race gave up for good after three attempts, and the winner died on a single failed renew or on any Redis connection error, releasing the lock with nobody left to take it over. From then on expired entries accumulated in the usage pool until a node restarted, so /api/usage over-reported models in use and every disconnect handler walked an ever-growing pool.

The task now retries lock acquisition forever like the session pool cleanup does, and any error is logged and answered by releasing the lock and returning to acquisition, so a transient failure costs one cleanup cycle and every node stays a takeover candidate. The delete of an emptied model entry is KeyError-guarded because a disconnect handler on another node can remove the same key between the sweep's snapshot and its delete; unguarded, that race was a permanent task killer that needed nothing rarer than a chat finishing while its tab closed.

2026-08-20 12:59:38 -07:00

..

main.py

fix: keep the usage pool cleanup task alive across lock loss and Redis errors (#28834)

2026-08-20 12:59:38 -07:00

utils.py

perf: optional orjson JSON codec behind ENABLE_ORJSON (#27583)

2026-07-27 03:45:37 -04:00