Bug #107920 | exception 0xc0000005 | ||
---|---|---|---|
Submitted: | 20 Jul 2022 7:45 | Modified: | 21 Jul 2022 8:46 |
Reporter: | Luigi Cangiano | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Archive storage engine | Severity: | S2 (Serious) |
Version: | 8.0.29 | OS: | Windows (Windows Server 2016 Datacenter) |
Assigned to: | CPU Architecture: | Any |
[20 Jul 2022 7:45]
Luigi Cangiano
[20 Jul 2022 7:47]
Luigi Cangiano
Structure of the log schema
Attachment: log schema.sql (application/octet-stream, text), 15.82 KiB.
[20 Jul 2022 7:48]
Luigi Cangiano
MySQL configuration file
Attachment: my.ini (application/octet-stream, text), 22.46 KiB.
[20 Jul 2022 12:48]
MySQL Verification Team
Hi Mr. Cangiano, Thank you for your bug report. We have run your test case, including the mentioned SELECT. We have also adjusted our settings to you my.ini. However , we were totally unable to repeat your problem or to get any exception. We have also searched all bugs for the stacktrace like yours and we have found none. Can't repeat.
[20 Jul 2022 14:58]
Luigi Cangiano
backup script runs once per day
Attachment: backup.cmd (application/octet-stream, text), 944 bytes.
[20 Jul 2022 15:00]
Luigi Cangiano
the problem occurs on average every 15-20 days, the mysql service is terminated and the only way to resume normal operation is to delete the 'log' schema and recreate it. This obviously results in data loss. The server in question is both master and slave in a replication process and, in this case, the 'log' schema receives data from all currently configured slaves (19). This means that the 'log' schema tables grow continuously. I doubt that the problem can be related to the amount of data contained by the tables of the 'log' schema. But I have no idea what the trigger could be.
[21 Jul 2022 6:07]
MySQL Verification Team
Good general rule of thumb is don't use the ARCHIVE engine for any valuable data. It's not designed to be reliable and is hardly maintained anymore. Probably some corruption on that table.
[21 Jul 2022 8:46]
Luigi Cangiano
No words on the documentation about the fact the Archive storage engine is "hardly" mantained or "not reliable". This storage engine seems perfect for managing logs or data that will never be modified and/or deleted. I'll use a different engine (MyISAM maybe) but in any case I think the documentation needs updating. Others may run into the same issue.