Project

General

Profile

Actions

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 over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Viktor Gurov
Category:
XMLRPC
Target version:
Start date:
11/19/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.05
Release Notes:
Default
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.

Actions

Also available in: Atom PDF