Project

General

Profile

Feature #10731

XML-sync primary/secondary config flag

Added by Constantine Kormashev 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Very Low
Assignee:
-
Category:
XMLRPC
Target version:
-
Start date:
07/06/2020
Due date:
% Done:

0%

Estimated time:

Description

To prevent XML-sync misconfiguring on a HA cluster, it would be good to make a config flag that can be used for distinguishing primary and secondary nodes. It might be a hidden flag in the config, which is set to primary if XML-sync is enabled on the node and after propagated to another node as secondary, and vice versa. If the node's flag is secondary, then its XML-sync menu is blocked. This flag can be also used for other purposes. E.g. it might be evidence of init XML-sync was successful and so on.

There is a small issue here, flag on secondary is propagated by primary, that means if we would like to clear secondary role without a primary, then we need something like a Red Force Clear button, which can reset the flag.
The other way would be clearing the secondary flag each reboot and keep it unflagged until the 1st XML-sync session, but this is less obvious.

History

#1 Updated by Jim Pingle 4 months ago

  • Category set to XMLRPC

Also available in: Atom PDF