{"version":"2.1.274","anchor":"gateway-open-request-backpressure-warning","canonical_anchor":"gateway-open-request-backpressure-warning","heading":"Self-hosted gateway now warns about request backpressure","tier":"internal","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/gateway-open-request-backpressure-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Self-hosted gateway now warns about request backpressure\n\nThe self-hosted gateway logs a throttled warning when open client requests outpace what it can forward upstream\n\n**What**\n\nThe self-hosted-runner gateway process now tracks how many client requests are currently open compared to how many it is able to forward upstream at the same time. When the number of open requests exceeds the configured (or default) outbound concurrency limit, it logs a rate-limited warning.\n\nThe warning suggests either adding more replicas or raising `BUN_CONFIG_MAX_HTTP_REQUESTS`, along with the replica's memory limit, to allow more concurrent outbound requests.\n\n**Why**\n\nThis helps operators running a self-hosted gateway notice and diagnose a bottleneck before it causes request failures or timeouts, and points them directly at the two knobs (replica count and `BUN_CONFIG_MAX_HTTP_REQUESTS`) that can relieve it.\n\n- Area: Gateway\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}