From dfab4794ecd44d1b53b8d8fec85fb2e4375b2e73 Mon Sep 17 00:00:00 2001 From: Anmol Jaiswal <68013660+anmolg1997@users.noreply.github.com> Date: Fri, 11 Sep 2026 22:52:32 +0530 Subject: [PATCH] docs(router): name both affinity TTL knobs in the _claim_pin docstring (#40663) The docstring cited session_affinity_ttl_seconds as the keepalive bound, but the Router-level knob feeding ttl_seconds is deployment_affinity_ttl_seconds; session_affinity_ttl_seconds is the separate per-request PreRoutingHookResponse override. Anyone grepping the docstring's name to shrink the Router default finds only the override. Name both, scoped correctly. --- .../router_utils/pre_call_checks/deployment_affinity_check.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/litellm/router_utils/pre_call_checks/deployment_affinity_check.py b/litellm/router_utils/pre_call_checks/deployment_affinity_check.py index 6f3ea8eb78a..c7eb46046ef 100644 --- a/litellm/router_utils/pre_call_checks/deployment_affinity_check.py +++ b/litellm/router_utils/pre_call_checks/deployment_affinity_check.py @@ -349,7 +349,9 @@ class DeploymentAffinityCheck(CustomLogger): first write instead of the last. Re-claiming with the stored value refreshes its TTL, the same keepalive the complexity router's model pin documents: an active session must not lose its pin mid-conversation just because it outlives the - original write, so `session_affinity_ttl_seconds` bounds idle time, not total + original write, so the affinity TTL (the Router's + `deployment_affinity_ttl_seconds`, or a pre-routing hook's per-request + `session_affinity_ttl_seconds` override) bounds idle time, not total session length. On Redis one Lua script does the get-or-set-or-refresh atomically (same registration seam the rate limiters use) and the in-memory tier is synchronized to the winner; without Redis, and whenever Redis is