Hi,
Thanks for your work on this!
The ideal for upstream is if you can find a self-contained testcase we
can use to reproduce from scratch, i.e. something along the lines of:
* Set up master-slave replication
* Create a table with [columns] and 70k rows
* Run OPTIMIZE TABLE on the master
* Obs
2017-12-06 9:15 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>:
> What can I do next to further investigate this in order to provide
> feedback over here in an efficient way ?
Thinking aloud:
1. Share table structure
2. Copy table to another name, add optimize table for the copy and see
if it
2017-12-01 10:32 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>:
> I reactivated one set of optimize queries for this night and it crashed
> with the exact same backtrace. So I can confirm this is indeed related
> to this specific set. However, there is nothing fancy about them at all.
Nice!
I
2017-11-30 9:12 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>:
> @Olaf: it wasn't available anymore unfortunately.
>
> After deactivating the OPTIMIZE statements and changing the TRUNCATE
> statement to DELETE FROM in our pre-production scripts, I can happily
> confirm there was no outage on o
2017-11-29 10:46 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>:
> @ChristianEhrhardt
> Thanks for your replies and initiatives. Much appreciated.
> I did indeed notice the install package we could rollback to using apt-get
> install mysql-server=XXX was 5.7.11, but this version is more than a
2017-11-03 10:55 GMT+01:00 ChristianEhrhardt <1729...@bugs.launchpad.net>:
> 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 i
