Bug #94812 mysql 5.7.22 crash

• Submitted: 28 Mar 2019 10:12
• Modified: 23 Apr 2019 14:55
• Reporter: Kevin Zhang
• Status: Can't repeat
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 5.7.22
• OS: Red Hat (6.5)
• CPU Architecture: Any
• Tags: 5.7.22, crash

[28 Mar 2019 10:12] Kevin Zhang

Description:
environment：
OS：Red Hat Enterprise Linux Server release 6.5 (Santiago)
MySQL version：5.7.22
Questions：I use pt-online-schema-change to cause the mysqld service to restart when adding an index in a table with 50 million records.
SQL:
INSERT LOW_PRIORITY IGNORE INTO `ugcdata`.`_t_migu_playlist_new` (`playlistid`, `channel`, `createuserid`, `playlisttype`, `playlistname`, `summary`, `image`, `isdefault`, `status`, `createtime`, `updatetime`, `imagechangetype`, `contentcount`, `colleccount`, `sharecount`, `playcount`, `commcount`, `hotspot`) SELECT `playlistid`, `channel`, `createuserid`, `playlisttype`, `playlistname`, `summary`, `image`, `isdefault`, `status`, `createtime`, `updatetime`, `imagechangetype`, `contentcount`, `colleccount`, `sharecount`, `playcount`, `commcount`, `hotspot` FROM `ugcdata`.`t_migu_playlist` FORCE INDEX(`PRIMARY`) WHERE ((`playlistid` >= '100626545')) AND ((`playlistid` <= '100634459')) LOCK IN SHARE MODE /*pt-online-schema-change 22816 copy nibble*/

How to repeat:
unknow

[28 Mar 2019 10:13] Kevin Zhang

mysqld err log

Attachment: crash-log.png (image/png, text), 63.55 KiB.

[28 Mar 2019 10:14] Kevin Zhang

crash sql

Attachment: crash-sql.png (image/png, text), 36.32 KiB.

[28 Mar 2019 10:14] Kevin Zhang

mysql err log

Attachment: mysqld.err.txt (text/plain), 42.99 KiB.

[10 Apr 2019 13:13] MySQL Verification Team

Hi 开威 张,

Thank you for your bug report.

First of all, you are using 5.7.22, which is not latest patch-build release. Hence, try doing that ALTER with latest release, so that we do not finish up chasing old, already fixed bugs.

Second, check mysql error log and all server logs. There is a possibility that you have run out of disk space or ran out of your quota, out of memory or similar.

Last, but not least, we need a fully repeatable test case in order to verify your bug. Please, try to come up with a test case containing the smallest number of rows that will lead to the crash.

Test case should consist of a number of SQL commands that would lead to the crash that you are writing about.

[19 Apr 2019 8:59] Kevin Zhang

hardware,table meta...

Attachment: informations.txt (text/plain), 282.98 KiB.

[19 Apr 2019 9:03] Kevin Zhang

The company does not agree to give the data.

[23 Apr 2019 14:55] MySQL Verification Team

HI 开威 张,

Sorry, but we can not verify the bug, without repeating it.

We do not require all of data, but we do require a minimum set of data which would repeat the behaviour.

Please, let us know when you upload the data.