Project

General

Profile

Actions
Copy link

Feature #13805

open

A way to reliably determine if system is the primary or secondary in CARP

Added by Christopher Cope almost 2 years ago. Updated 9 months ago.

Status:
New
Priority:
Very Low
Assignee:
Christopher Cope
Category:
High Availability
Target version:
Future
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

There is no current way, as far as I can tell, to reliably determine if the current system is the primary or secondary.

A few of the current ways include:
  • "Synchronize Config to IP" isn't set it's likely secondary, but isn't certain.
  • Checking the advskew is a good way, but these are sometimes changed, so it isn't 100% either.

My thoughts are to add a setting to System > High Avail. Sync for Primary/Secondary.

This would allow behavior specific to that to be implemented. Such as:
  • Disabling the ability to toggle CARP maintenance mode on the Secondary, to avoid confusion.
  • Auto filling advskew when creating new VIPs
  • etc.

I could write the code and submit a merge request for this, but would appreciate any thoughts / comments on anything I may be missing before I do that.

Actions
Copy link

Also available in: Atom PDF