Problem
In the Flight ingress path, session creation can be triggered repeatedly when requests arrive without a reusable x-duckgres-session token context. Under bursty traffic, this causes rapid growth in active sessions/workers before idle reaping catches up.
Because sessions remain alive for the configured idle window, concurrency effectively scales with request rate multiplied by idle TTL. This can hit max-workers limits and produce ResourceExhausted/max workers reached failures for otherwise valid requests.
This is observable even outside explicit transactions, and it can happen with repeated requests from the same database user when request-to-request session continuity is not preserved across Flight RPC calls.
Problem
In the Flight ingress path, session creation can be triggered repeatedly when requests arrive without a reusable
x-duckgres-sessiontoken context. Under bursty traffic, this causes rapid growth in active sessions/workers before idle reaping catches up.Because sessions remain alive for the configured idle window, concurrency effectively scales with request rate multiplied by idle TTL. This can hit max-workers limits and produce
ResourceExhausted/max workers reachedfailures for otherwise valid requests.This is observable even outside explicit transactions, and it can happen with repeated requests from the same database user when request-to-request session continuity is not preserved across Flight RPC calls.