On 2012-09-04T15:56:14, Stefan Schloesser <[email protected]> wrote:
> Hi,
>
> I would like to know what the recommended way is to update a cluster. Every
> week or so bug fixes and security patches are released for a various parts of
> the used software.
I prefer rolling upgrades; migrate service, stop cluster, update
software (reboot node if necessary), restart cluster. Repeat with next
node until all cluster nodes are updated.
> Sounds complex and thus error prone to me. The problem seems to me that e.g.
> in a release upgrade scenario the mysql binary must match its data version
> for it to work correctly.
The problem indeed arises when the upgraded service up-converts its data
so that a rollback to a previous version is not feasible. In that case,
taking a snapshot before the upgrade is a good idea.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
