Re: Mysql 5.1.36 cluster - does anybody have this working?

[Howard Wilkinson <howard@xxxxxxxxxxx>]

Itamar Reis Peixoto wrote:

I can recommend you mysql master-slave replication

or postgresql with bucardo (2 master's, and more n slaves)




On Thu, Aug 20, 2009 at 10:13 AM, Howard Wilkinson<howard@xxxxxxxxxxx> wrote:
  

  I have upgraded from FC9 through FC10 to FC11 but the cluster code
available with FC11 is refusing to start up properly. Does anybody have this
working? If so was there any magic incantations used to get the database
gods to cooperate?

Regards, Howard.

    

Itamar,

I already use the master-slave replication for some of our higher volume databases - although this in itself brings in problems when things get out of step.

But I use the cluster storage for our smaller configuration databases, including the backend to a replciated MyDNS environment. This has worked wonderfully with the 5.0.x series of MySQL but in upgrading to 5.1.36 a number of problems arose.

When I sent out the message I still had part of the cluster running 5.0.x storage, and the new Cluster nodes were refusing to come up. I finally fixed this by altering the parameters to allow the 5.0.x nodes to start under control of the 5.1.36 NDB_MGMD instances (Options that had reasonable defaults for .5.0.x do not if they are provided by a 5.1.36 arbitrator) once these old nodes started I got a sensible error message from the 5.1.36 NDBD nodes - they told me that the cluster version were incompatible - it seems you need to upgrade to an early 5.1.x cluster first and then go through 5.1.20 (or 5.1.21 or something thereabouts) and the jump to 5.1.36 to do a hot upgrade, and even then I have found little evidence of anybody doing it.

So what I did instead was to shutdown the 5.0.x NDB stores, destroy the NDB store on the 5.1.36 nodes, start these nodes with the --initial-state --nowait-nodes arguments and rebuilding the NDB store from our backups. I could then upgrade the 5.0.x nodes knowing that I had a working store and like magic everything burts into life when I brought up the quorum.

So the lesson learnt is that you cannot jump major versions using the upgrade paths suggested by MySQL unless you track their upgrade steps - even then I am not sure it would be easy. They use different database gods with each major release :-[

Regards, Howard.

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines