Hello, I think, that only way is to upgrade manually and can not without 
downtime. My way will be to put cluster to maintanance mode and perform upgrade 
on active node with mysql_upgrade cmd. On pasive node should be enough to just 
install newer mysql without starting it and running mysql_upgrade. But you can 
make second node primary, mount fs and them run standard mysql upgrade lik eon 
active node was.

S pozdravem Kristián Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: [email protected]

www.feldhost.cz - FeldHost™ – profesionální hostingové a serverové služby za 
adekvátní ceny.

FELDSAM s.r.o.
V rohu 434/3
Praha 4 – Libuš, PSČ 142 00
IČ: 290 60 958, DIČ: CZ290 60 958
C 200350 vedená u Městského soudu v Praze

Banka: Fio banka a.s.
Číslo účtu: 2400330446/2010
BIC: FIOBCZPPXX
IBAN: CZ82 2010 0000 0024 0033 0446

> On 12 Oct 2017, at 20:42, Attila Megyeri <[email protected]> wrote:
> 
> Hi, This does not really answer my question. Placing the cluster into 
> maintenance mode just avoids monitoring and restarting, but what about the 
> things I am asking below? (data dir related questions)
>  
> thanks
>  
>   <>
> From: Kristián Feldsam [mailto:[email protected]] 
> Sent: Thursday, October 12, 2017 7:51 PM
> To: Attila Megyeri <[email protected]>; [email protected]
> Subject: Re:[ClusterLabs] Mysql upgrade in DRBD setup
>  
> hello, you should put cluster to maintenance mode
>  
>  
>  
> Sent from my MI 5
> On Attila Megyeri <[email protected] 
> <mailto:[email protected]>>, Oct 12, 2017 6:55 PM wrote:
> Hi all,
>  
> What is the recommended mysql server upgrade methodology in case of an 
> active/passive DRBD storage?
> (Ubuntu is the platform)
>  
> 1)      On the passive node the mysql data directory is not mounted, so the 
> backup fails (some postinstall jobs will attempt to perform manipulations on 
> certain files in the data directory).
> 2)      If the upgrade is done on the active node, it will restart the 
> service (with the service restart, not in a crm managed fassion…), which is 
> not a very good option (downtime in a HA solution). Not to mention, that it 
> will update some files in the mysql data directory, which can cause strange 
> issues if the A/P pair is changed – since on the other node the program code 
> will still be the old one, while the data dir is already upgraded.
>  
> Any hints are welcome!
>  
> Thanks,
> Attila

_______________________________________________
Users mailing list: [email protected]
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to