Bug #11082
HA setup restarts all OpenVPN instances on the secondary after making any change on the primary
Status:
Pull Request Review
Priority:
Normal
Assignee:
Category:
High Availability
Target version:
Start date:
11/19/2020
Due date:
% Done:
0%
Estimated time:
Affected Version:
All
Affected Architecture:
Description
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.
History
Updated by #2
Updated by Jim Pingle 2 months ago
Updated by - 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.
#3
Updated by Renato Botelho 2 months ago
Updated by - Assignee set to Viktor Gurov
#4
Updated by Danilo Zrenjanin about 2 months ago
Updated by 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.
#5
Updated by Ferran Peinado 1 day ago
Updated by Hello everyone,
This issue is also affecting us, do you know approximately when an official update is going to fix this issue?
Many thanks