From e05a7a3655611b90fa8aa8b359a05c49f65971c0 Mon Sep 17 00:00:00 2001 From: Yucheng Zhu Date: Mon, 27 Jul 2026 12:30:06 -0700 Subject: [PATCH] docs(otel/v2): correct stale _MAX_CACHED_PROVIDERS comment on eviction The comment still described flushing and shutting down evicted providers; the eviction now drops the reference without a synchronous shutdown. Greptile nit on the current head. --- litellm/integrations/otel/plumbing/routing.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/litellm/integrations/otel/plumbing/routing.py b/litellm/integrations/otel/plumbing/routing.py index 0009a67146a..e36d5f4b10a 100644 --- a/litellm/integrations/otel/plumbing/routing.py +++ b/litellm/integrations/otel/plumbing/routing.py @@ -44,9 +44,9 @@ _NON_OTLP_KINDS = ("console", "in_memory", "inmemory", "memory") # Cap on distinct destination-scoped providers held at once. Destinations are # admin-owned (one per key/team), so this is resource hygiene rather than an -# anti-abuse bound: it keeps the working set of active tenants resident while -# flushing and shutting down evicted providers so their exporter threads are -# reclaimed. +# anti-abuse bound: it keeps the working set of active tenants resident. Evicted +# providers are dropped without a synchronous shutdown (see _evict_if_full); their +# exporter threads drain on their own and are reclaimed at process exit. _MAX_CACHED_PROVIDERS = 256