Feature #55544
Make it possible to use custom haproxy config when using ingress
0%
Description
We have a use case where the default haproxy client and server timeouts set here0 are too low and cause connection resets for around 3% of our write requests.
We tried Increasing the timeouts(by editing the haproxy file inside the docker container and reloading haproxy) to 900s which dropped the error rate to around 0.3%.
This is error prone and cumbersome to manage in the long term.
Can you make it possible to override the haproxy.cfg or the haproxy.cfg.j2 template file when using cephadm and ceph ingress service so we can tune it according to our needs?
History
#1 Updated by Redouane Kachach Elhichou over 1 year ago
- Status changed from New to Need More Info
cephadm already allows using your own haproxy.cfg:
ceph config-key set mgr/cephadm/services/ingress/haproxy.cfg -i <custom-haproxy-config> ceph orch redeploy <ingress-service-name>
Please have a look to: https://docs.ceph.com/en/quincy/cephadm/services/monitoring/#using-custom-configuration-files
.. if you still think the current support doesn't cover your needs please free to reopen.
#2 Updated by Redouane Kachach Elhichou over 1 year ago
- Status changed from Need More Info to Closed
#3 Updated by Madushan Nishanta over 1 year ago
Redouane Kachach Elhichou wrote:
cephadm already allows using your own haproxy.cfg:
[...]
Please have a look to: https://docs.ceph.com/en/quincy/cephadm/services/monitoring/#using-custom-configuration-files
.. if you still think the current support doesn't cover your needs please free to reopen.
Interesting, this wasn't very clear on the docs. Thank you for pointing this out. I'll test it.
#4 Updated by Madushan Nishanta over 1 year ago
Tested it, it works okay. The config-key has to be in .j2 template format.