| Bug #91036 | mysql 8.0.11 innodb corrupt after sysbench failed | ||
|---|---|---|---|
| Submitted: | 27 May 2018 4:45 | Modified: | 9 Jul 2018 16:57 |
| Reporter: | li zhenxu | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 8.0.11 | OS: | Any (3.10.0-514.26.2.el7.x86_64) |
| Assigned to: | CPU Architecture: | x86 | |
[27 May 2018 4:45]
li zhenxu
[9 Jul 2018 16:57]
MySQL Verification Team
Hi, I have run your test on 8.0.11 like this: ./sysbench oltp_read_write.lua --mysql-host=127.0.0.1 --mysql-port=3306 --mysql-db=test --mysql-user=myuser --mysql-password=mypassword --table_size=1000000 --tables=100 --threads=50 --report-interval=10 --time=300 prepare And everything ran just fine .... these are the last lines: Inserting 1000000 records into 'sbtest75' Creating a secondary index on 'sbtest37'... Creating a secondary index on 'sbtest3'... Creating table 'sbtest87'... Inserting 1000000 records into 'sbtest87' Creating table 'sbtest53'... Inserting 1000000 records into 'sbtest53' Creating a secondary index on 'sbtest39'... Creating table 'sbtest89'... Inserting 1000000 records into 'sbtest89' Creating a secondary index on 'sbtest6'... Creating table 'sbtest56'... Inserting 1000000 records into 'sbtest56' Creating a secondary index on 'sbtest43'... Creating table 'sbtest93'... Inserting 1000000 records into 'sbtest93' Creating a secondary index on 'sbtest50'... Creating table 'sbtest100'... Inserting 1000000 records into 'sbtest100' Creating a secondary index on 'sbtest40'... Creating table 'sbtest90'... Inserting 1000000 records into 'sbtest90' Creating a secondary index on 'sbtest24'... Creating table 'sbtest74'... Inserting 1000000 records into 'sbtest74' Creating a secondary index on 'sbtest17'... Creating table 'sbtest67'... Inserting 1000000 records into 'sbtest67' Creating a secondary index on 'sbtest69'... Creating a secondary index on 'sbtest83'... Creating a secondary index on 'sbtest55'... Creating a secondary index on 'sbtest77'... Creating a secondary index on 'sbtest65'... Creating a secondary index on 'sbtest62'... Creating a secondary index on 'sbtest84'... Creating a secondary index on 'sbtest91'... Creating a secondary index on 'sbtest96'... Creating a secondary index on 'sbtest76'... Creating a secondary index on 'sbtest54'... Creating a secondary index on 'sbtest88'... Creating a secondary index on 'sbtest85'... Creating a secondary index on 'sbtest60'... Creating a secondary index on 'sbtest66'... Creating a secondary index on 'sbtest81'... Creating a secondary index on 'sbtest94'... Creating a secondary index on 'sbtest89'... Creating a secondary index on 'sbtest95'... Creating a secondary index on 'sbtest80'... Creating a secondary index on 'sbtest86'... Creating a secondary index on 'sbtest70'... Creating a secondary index on 'sbtest79'... Creating a secondary index on 'sbtest97'... Creating a secondary index on 'sbtest59'... Creating a secondary index on 'sbtest78'... Creating a secondary index on 'sbtest92'... Creating a secondary index on 'sbtest57'... Creating a secondary index on 'sbtest61'... Creating a secondary index on 'sbtest73'... Creating a secondary index on 'sbtest72'... Creating a secondary index on 'sbtest58'... Creating a secondary index on 'sbtest75'... Creating a secondary index on 'sbtest63'... Creating a secondary index on 'sbtest51'... Creating a secondary index on 'sbtest64'... Creating a secondary index on 'sbtest93'... Creating a secondary index on 'sbtest99'... Creating a secondary index on 'sbtest68'... Creating a secondary index on 'sbtest82'... Creating a secondary index on 'sbtest74'... Creating a secondary index on 'sbtest98'... Creating a secondary index on 'sbtest52'... Creating a secondary index on 'sbtest87'... Creating a secondary index on 'sbtest90'... Creating a secondary index on 'sbtest56'... Creating a secondary index on 'sbtest67'... Creating a secondary index on 'sbtest71'... Creating a secondary index on 'sbtest100'... Creating a secondary index on 'sbtest53'...
[10 Jul 2018 13:50]
Roger li
hi, Sinisa Milivojevic,
my mysql is mgr. as fellow:
mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+-------------+----------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION |
+---------------------------+--------------------------------------+-------------+-------------+--------------+-------------+----------------+
| group_replication_applier | 25d0899d-5eff-11e8-a6bf-00163e007fde | enmodb2 | 3306 | ONLINE | PRIMARY | 8.0.11 |
| group_replication_applier | 4f89cd14-5eff-11e8-adf8-00163e004de6 | enmodb3 | 3306 | ONLINE | PRIMARY | 8.0.11 |
| group_replication_applier | b3dfe8d1-64b2-11e8-be29-00163e005628 | enmodb1 | 3306 | ONLINE | PRIMARY | 8.0.11 |
+---------------------------+--------------------------------------+-------------+-------------+--------------+-------------+----------------+
3 rows in set (0.01 sec)
I haved rebuild the database.
[10 Jul 2018 14:53]
MySQL Verification Team
Hi, What do you mean that MySQL is manager ??? Is it master or slave ??? Hence , does this crash happens on the master or slave ?? Or are you using MySQL GR, also known as InnoDB Cluster. In that case, please state which machine exactly crashes in the Cluster. Draw the topology of the GR and let us know which MySQL exactly crashes on sysbench oltp read-write test.
