On 09/05/2012 01:26 AM, Stefan Schloesser wrote:

> my problem with the rolling upgrade is the drbd partition. If you
migrate the service its data will move too. If you then restart the
cluster and migrate back the data will not be in an upgraded state and
thus not match the binary. Hence you can't be sure your service will
start on the recently upgraded node with the old data version.

I think if your requirements are zero downtime and a database engine
that's not compatible with itself, your only option is to not upgrade.
Otherwise one or the other has to go.

HTH
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to