Just tried on my environment :
Centos7.8 RDO deploy with Kolla-Ansible Stein release
2 network node with Haproxy and keepalived
3 Ctrl nodes with Keystone
3 BDD node with Rabbit & Galera
net.ipv4.tcp_retries2 default value :15 retries
Steps i followed :
Generate some loops requests to keystone .
Log onto the master keepalived with Vip public and private
Shutoff the keepalived container
=> VIP was recreated almost instant on the other network controler
Logs on Keystone
Lost access to the Vip Database <= maybe it is different configuration from you, but all services are connected under the Mariadb VIP
Requests to keystone was stuck during 180sec
Second test
net.ipv4.tcp_retries2 set to 10
Request to keystone was during 120sec
Third test
net.ipv4.tcp_retries2 set to 5
Request to keystone was during 60sec
So, you are right , we can tune the failover of the VIP Haproxy with this tuning !!
I will do another tests , for me 180sec to failover was acceptable.
Hello,
Just tried on my environment :
Centos7.8 RDO deploy with Kolla-Ansible Stein release
2 network node with Haproxy and keepalived
3 Ctrl nodes with Keystone
3 BDD node with Rabbit & Galera
net.ipv4. tcp_retries2 default value :15 retries
Steps i followed :
Generate some loops requests to keystone .
Log onto the master keepalived with Vip public and private
Shutoff the keepalived container
=> VIP was recreated almost instant on the other network controler
Logs on Keystone
Lost access to the Vip Database <= maybe it is different configuration from you, but all services are connected under the Mariadb VIP
Requests to keystone was stuck during 180sec
Second test tcp_retries2 set to 10
net.ipv4.
Request to keystone was during 120sec
Third test tcp_retries2 set to 5
net.ipv4.
Request to keystone was during 60sec
So, you are right , we can tune the failover of the VIP Haproxy with this tuning !!
I will do another tests , for me 180sec to failover was acceptable.
Greeting
Stephane Chalansonnet