Project

General

Profile

Actions

Feature #3013

closed

Better upgrading for a CARP cluster

Added by Jerome Alet about 11 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
Start date:
05/29/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Not sure if this is a bug or something we do incorrectly, so I've added this issue as "Feature".

While upgrading a 2 nodes CARP cluster, we usually upgrade the slave first, and then if all goes well after reboot and packages reinstallation we upgrade the master. The problem is that once the master reboots, all its network interfaces automatically go to CARP MASTER state even before packages begin to be reinstalled, causing some functionnalities which were handled by the slave during the master's reboot to not work anymore, possibly for a long time if there is a lot of packages to download and reinstall.

Couldn't the master be artificially kept in CARP BACKUP mode until all packages have been reinstalled and started ?

Actions

Also available in: Atom PDF