HA setup restarts all OpenVPN instances on the secondary after making any change on the primary
Pull Request Review
Maybe there is no need for restarting OpenVPN instances on the secondary if there weren't any changes related to VIP or OpenVPN settings on the primary.
The way it works now is just fine as long as there are no many OpenVPN servers/clients. With a high number of instances, XMLRPC starts having issues due to the time it takes to restart them all after any changes on the Primary.
- Status changed from New to Pull Request Review
- Target version changed from 2.5.0 to 2.5.next
Probably too late to work this in to 2.5.0 given the potential impact.
- Assignee set to Viktor Gurov
We have a customer with a very complex HA setup, who has implemented the new xmlrpc.php file. It works stable and fixed the issue reported here.
This issue is also affecting us, do you know approximately when an official update is going to fix this issue?
Also available in: Atom