Hi Olaf,
there seem to be some related known issues in percona/mysql, see bug 1399471 for more details and follow referenced further bugs from there.
I'll explicitly subscribe Lars to take a look, but as printed in the error message it would be great if you could file (and mention the number here) a bug at [1] the upstream bug tracker for mysql. They might have a backportable fix known already.
You'd have to check if [2] or [3] are your case already.
In general many of the issues seem related to e.g. migrating from percona - does your setup have any percona history that could be related?
Hi Olaf,
there seem to be some related known issues in percona/mysql, see bug 1399471 for more details and follow referenced further bugs from there.
I'll explicitly subscribe Lars to take a look, but as printed in the error message it would be great if you could file (and mention the number here) a bug at [1] the upstream bug tracker for mysql. They might have a backportable fix known already.
You'd have to check if [2] or [3] are your case already.
In general many of the issues seem related to e.g. migrating from percona - does your setup have any percona history that could be related?
[1]: http:// bugs.mysql. com /bugs.mysql. com/bug. php?id= 69274 /bugs.mysql. com/bug. php?id= 68987
[2]: https:/
[3]: https:/