We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
本地测试 http 1.1 转发,发现bfe貌似会一直保持和后端服务之间的tcp连接,每条连接会占用2条协程,导致空闲后 协程也还在。
bfe能否支持配置 空闲连接超时时间,超时后自动断开。也就是标准库里面的 http.Transport IdleConnTimeout
// IdleConnTimeout is the maximum amount of time an idle // (keep-alive) connection will remain idle before closing // itself. // Zero means no limit.
The text was updated successfully, but these errors were encountered:
很好的建议。我们后续会考虑一下这个需求。谢谢。
Sorry, something went wrong.
问题 本地测试 http 1.1 转发,发现bfe貌似会一直保持和后端服务之间的tcp连接,每条连接会占用2条协程,导致空闲后 协程也还在。 解决方案 bfe能否支持配置 空闲连接超时时间,超时后自动断开。也就是标准库里面的 http.Transport IdleConnTimeout // IdleConnTimeout is the maximum amount of time an idle // (keep-alive) connection will remain idle before closing // itself. // Zero means no limit.
是否可以补充下测试方法;另外测试中是否开启了连接池
No branches or pull requests
问题
本地测试 http 1.1 转发,发现bfe貌似会一直保持和后端服务之间的tcp连接,每条连接会占用2条协程,导致空闲后 协程也还在。
解决方案
bfe能否支持配置 空闲连接超时时间,超时后自动断开。也就是标准库里面的 http.Transport IdleConnTimeout
The text was updated successfully, but these errors were encountered: