Bug #11082
closed
XMLRPC synchronization restarts all OpenVPN instances on the secondary node when making any change on the primary node
100%
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.
Updated by Viktor Gurov 10 months ago
Updated by Jim Pingle 10 months ago
- 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.
Updated by Danilo Zrenjanin 10 months ago
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.
Updated by Ferran Peinado 8 months ago
Hello everyone,
This issue is also affecting us, do you know approximately when an official update is going to fix this issue?
Many thanks
Updated by Renato Botelho 7 months ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov 7 months ago
- % Done changed from 0 to 100
Applied in changeset 23fcdcccd369603f4af6a89a0ec0a81505173f40.
Updated by Jim Pingle 4 months ago
- 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.