[Openstack-operators] mysql crash during Juno upgrade when using Galera
Fischer, Matt
matthew.fischer at twcable.com
Wed Mar 11 12:25:17 UTC 2015
We were remiss for not mentioning this during our talk on Monday since apparently its happening to other folks as I found out last night at dinner. During the Juno database migrations we saw mysql crash. This ended up delaying our move to Juno by a few weeks while the bug was being worked. There is an upstream bug already filed for this and it was fixed after some work by Percona. The upstream bug is a bit non-obviously named, but here it is: https://bugs.launchpad.net/percona-xtradb-cluster/5.5/+bug/1282707
The manifestation is that when you’re upgrading the databases, mysql dies with a stack trace similar to the bug. We did not see this in our fresh dev environments where we did all our testing because we didn’t have enough data presumably, we only saw it in real systems that had been operating for awhile. Once we pulled in prod databases into our dev environments the bug was 100% reproducible.
For ubuntu, its fixed in the percona experimental repo as version 5.6.21-25.8-939.trusty, we’ve been running this since the day it was released on Jan 29 without issue. It also looks like a March 9 version is in percona main which should also include the fix but I have not confirmed and that’s not noted in the bug.
________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150311/493ec56f/attachment.html>
More information about the OpenStack-operators
mailing list