Our Problem is that the default TCP timeouts aren't working for some of our usecases.
First Idea
The idea is to add three custom timeout parameter to the createLoadBalancer method.
timeout connect
timeout client
timeout server
Second Idea
The second idea is to take a custom parameter to extend the listen section in haproxy.
This custom parameter would be an array of configuration strings which get validated with haproxy configtest.
@joschi36 Are you still considering this? please add configuration examples of what you want to achieve on the backend(s) with your new parameters, and a matrix of parameter <-> results. I think it might be a good idea but it is a bit vague as you describe it so far.
Activity
DaanHoogland commented on Dec 11, 2020
@joschi36 Are you still considering this? please add configuration examples of what you want to achieve on the backend(s) with your new parameters, and a matrix of parameter <-> results. I think it might be a good idea but it is a bit vague as you describe it so far.
weizhouapache commented on Dec 11, 2020
@DaanHoogland this should be fixed by #4141
DaanHoogland commented on Dec 11, 2020
ah right, can you check the PR, @joschi36 ? if this satisfies your request we'll close this when merged.
joschi36 commented on Dec 28, 2020
Yes this satisfies the request.
Can't wait to see this merged 😃
yadvr commented on Sep 21, 2021
Moving this to 4.17 as PR is moved to 4.17 milestone
7 remaining items
DaanHoogland commented on Jul 4, 2025
@joschi36 @CharlesQueiroz this is very stale and the PR is having conflicts. Are you guys still looking at this?
DaanHoogland commented on Jan 5, 2026
should be addressed with #11468
weizhouapache commented on Jan 5, 2026
actually ... #11468 only addressed the SSL offloading, not the haproxy settings
DaanHoogland commented on Jan 6, 2026
Should we re-open? Are there any plans for haproxy settings in scope ?