Adam Dixon wrote:
Hi guys,
This is now a fixed bug; http://bugs.mysql.com/bug.php?id=18118
Now I am looking at upgrading from 5.0.15 to 5.0.20a so that this bug
can no longer effect our cluster. So I have two questions;
How do I 'work-around' this bug in particular during the upgrade
process, eg ensure that the buffer overflow does not occur when I shut
the elected Master node down? Will minimising transactions on the
cluster do this?
Clever question...
on all mgmsrv's will do the trick.
after you upgraded all your datanodes, you can set it back
and;
I was wondering if there was anything special to look out for that may
not work correctly when going from 5.0.15 to 5.0.20a. I tested doing
this on a small 2-ndbd cluster and it seemed to work fine, I was just
wonder if there was any hidden gotchas in regards to jumping 5 minor
releases in one go?
Not that I know of...
/Jonas
5 messages in com.mysql.lists.clusterRe: Rolling restart full Crash 5.0.15
