Bug #11082
closed
XMLRPC synchronization restarts all OpenVPN instances on the secondary node when making any change on the primary node
Added by Danilo Zrenjanin about 4 years ago.
Updated over 3 years ago.
Plus Target Version:
21.05
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.
- Status changed from New to Pull Request Review
- Target version changed from 2.5.0 to CE-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.
Hello everyone,
This issue is also affecting us, do you know approximately when an official update is going to fix this issue?
Many thanks
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
- % Done changed from 0 to 100
- Target version changed from CE-Next to 2.6.0
- Plus Target Version set to 21.05
- Subject changed from HA setup restarts all OpenVPN instances on the secondary after making any change on the primary to XMLRPC synchronization restarts all OpenVPN instances on the secondary node when making any change on the primary node
- Category changed from High Availability to XMLRPC
Updating subject for release notes.
- Target version changed from 2.6.0 to 2.5.2
- Status changed from Feedback to Closed
Also available in: Atom
PDF
Updated by Viktor Gurov 
Updated by 
Updated by 
Updated by 
Updated by