envoyproxy/envoy

allow close downstream idle connection while draining

Open

#42,305 建立於 2025年11月30日

在 GitHub 查看
 (12 留言) (0 反應) (0 負責人)C++ (27,997 star) (5,373 fork)batch import
area/drainarea/listenerenhancementhelp wanted

描述

Description: When stopping envoy by using curl -X POST http://localhost:15000/drain_listeners?graceful Envoy only sending Connection: CLOSE on HTTP1, that means idle connection will be Established after idle_timeout at most.

Background: We are building AI Gateway based on Envoy, we hope idle_timeout could be large enough. Meanwhile we hope downstream idle connections could be closed as soon as possible, so that the the Gateway could be shutdown as early as possible.

[optional Relevant Links:] https://www.envoyproxy.io/docs/envoy/latest/operations/admin#operations-admin-interface-drain

Maybe close downstream idle connection could be the default behaviour or add a new configuration to enable it.

貢獻者指南

技術棧
cpp
領域
backendperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C++Envoy architectureHTTP connection drainingAdmin interface
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
The issue requests that when draining via POST /drain listeners?graceful, idle downstream connections should be closed immediately instead of waiting for idle timeout. Relevant source files include source/server/drain manager.cc and source/common/http/conn manager impl.cc. Comments discuss options: make it the default or add a new configuration flag. Investigate how idle connections are tracked and where the CLOSE header is set. Review existing tests for drain behavior and the admin handler in source/server/admin/drain handler.cc. A new config option might be introduced in the HCM or listener config.