Unfortunately, we had big hopes but we experienced again this exact bug,
with the exact same trace for version 5.1.21.
+-+
| VERSION() |
+-+
| 5.7.21-0ubuntu0.16.04.1-log |
+-+
Trace found in
@Andreas: It wasn't private before ... I don't have access to it anymore
either, even when I'm logged in the portal.
We proceeded with the update of MySQL to version 5.7.21 a few days ago.
We just reactivated the OPTIMIZE and TRUNCATE query for the run of
tomorrow morning.
I will post some
Apologies for my lack of feedback but those were quite busy days ...
A small update though: the bug I reported on the MySQL bugs has been set as
duplicate of the following on the bugs.mysql.com portal:
https://bugs.mysql.com/bug.php?id=88844
Severity is S1: critical.
** Bug watch added: MySQL
Hi Lars,
Thanks for your reply.
Please note that we experienced a crash again this morning, while all
optimise queries were removed from our batches ... so I fear it might be
misleading.
I will try to reproduce the crash in a VM.
In the meantime, please find our mysqld configuration file below:
Dears,
I finally finished narrowing it down to the single request causing the
crash.
I reactivated the TRUNCATE requests and those are working flawlessly. It
is an OPTIMIZE TABLE request on a table of about 7 entries that
causes the mysql service crash. It might be under use simultaneously,
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.
It is a simple SQL script with 9 OPTIMIZE statements being run from the mysql
@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 our server during this night.
If this can help investigating this bug in any
@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 year and a
half old, which doesn't sound like such a good idea.
Coming
Hi ChristianEhrhardt,
I went through the bug reports you mention, but this does not seem to
apply to what we are experiencing.
We also tried many approaches thinking there was some problem with the
data at first. The only thing we did not try yet is to recreate the
ibdata/ib_log files because it
Hi Olaf,
You are not alone ...
This bug did not occur on our systems when we were using version 5.7.19,
but since we upgraded to 5.7.20, we get this on a regular basis, but
still are unable to locate the exact cause.
I thought it was related specifically to replication, but according to
your
10 matches
Mail list logo
