HAProxy FAQ
约 1 分钟阅读
标签:FAQ
Memory Usage
- e.g.
- 16 kB buffers
- 34 kB/session
- 30000 sessions/GB
- 20000 sessions/GB - 考虑系统也会需要内存
perf debug
sysctl net.ipv4.ip_local_port_rangenet.core.wmem_max
net.core.rmem_max
net.ipv4.tcp_rmem
net.ipv4.tcp_wmemnbproc $(nproc)
req_ssl_sni vs ssl_fc_sni
- req_ssl_sni
- 用于 ssl paththrough 时
- 会比 hdr(host) 快一点点
- ssl_fc_sni
- 用于 ssl offload 时
use_backend s1 if { ssl_fc_sni my.domain.org }
use_backend s2 if { hdr(host) -i my2.domain.org }TLS handshake, Client hello 后无响应
在 AlpineLinux 3.14 上,Host 内运行 HAProxy,使用 SNI Passthrough 出现该问题,修改为在容器内运行后问题解决。 在容器内使用完全相同的 HAProxy 版本也没有问题,一次断定是 Host 环境的问题。
可能的原因
- 系统依赖升级后未重启
HAProxy exit code 143
- SIGTERM
cannot parse Content-Length: too long int
- H2, ssl-passthrough 时会有问题
- #1561GitHub Issuehaproxy/haproxy#1561
Cannot raise FD limit to 20637, limit is 4096.
ERR_HTTP2_SERVER_REFUSED_STREAM
- confluence.atlassian.com/jirakb/some-jira-pages-fail-to-render-or-some-actions-fail-to-complete-with-the-error-err_http2_server_refused_stream-1085441145.html
- opnsense/plugins#2013GitHub Issueopnsense/plugins#2013
- libressl
h3
Whitelist
acl white_list src 192.168.1.0/24 192.168.10.0/24
tcp-request content accept if white_list
tcp-request content reject关联信息
反向链接、本文链接的其他页面和外部资料。
References
GitHub3 条
- haproxy/haproxy#1561github.com/haproxy/haproxy/issues/1561
- haproxytech/kubernetes-ingress#546github.com/haproxytech/kubernetes-ingress/issues/546
- opnsense/plugins#2013github.com/opnsense/plugins/issues/2013
其他外链3 条
- confluence.atlassian.com/jirakb/some-jira-pages-fail-to-render-or-some-actions-fail-to-complete-with-the-error-err_http2_server_refused_stream-1085441145.htmlconfluence.atlassian.com/jirakb/some-jira-pages-fail-to-render-or-some-actions-fail-to-complete-with-the-error-err_http2_server_refused_stream-1085441145.html
- marc.info?l=haproxy&m=144490809910124&w=2marc.info/?l=haproxy&m=144490809910124&w=2
- sysadminxpert.com/what-is-haproxy-and-important-performance-factorssysadminxpert.com/what-is-haproxy-and-important-performance-factors