| Bug #94081 | Assertion failure: row0upd.cc:2123 | ||
|---|---|---|---|
| Submitted: | 27 Jan 14:55 | Modified: | 6 Mar 14:35 |
| Reporter: | wang huai | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S6 (Debug Builds) |
| Version: | 8.0.14 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | assertion, Failure, innodb, second index, UPDATE | ||
[27 Jan 15:47]
Shane Bester
It's a debug binary apparently..
#ifdef UNIV_DEBUG
mtr_commit(&mtr);
mtr_start(&mtr);
ut_ad(btr_validate_index(index, 0, false));
ut_ad(0); <--------
#endif /* UNIV_DEBUG */
[28 Jan 7:32]
wang huai
is this a problem? thanks .
[28 Jan 14:33]
Miguel Solorzano
When only debug build is affected the Severity could be S6 (Debug Builds) just that.
[5 Feb 17:02]
Sinisa Milivojevic
Hi, Can we please get a more precise information. Like, the exact sysbench command with all options, for how long to run, how to stop, how to restart etc.
[6 Mar 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: 42 2019-01-27T07:01:23.704112Z 16 [ERROR] [MY-012869] [InnoDB] Record in index `k_1` of table `sbtest`.`sbtest1` was not found on update: T UPLE (info_bits=0, 2 fields): {[4] (0x00070103),[4] (0x0007010F)} at: COMPACT RECORD(info_bits=0, 2 fields): {[4] (0x00070103), [4] (0x0007010E)} 43 2019-01-27T07:01:27.194049Z 16 [ERROR] [MY-013183] [InnoDB] Assertion failure: row0upd.cc:2123:0 thread 140736349599488 44 InnoDB: We intentionally generate a memory trap. 45 InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 46 InnoDB: If you get repeated assertion failures or crashes, even 47 InnoDB: immediately after the mysqld startup, there may be 48 InnoDB: corruption in the InnoDB tablespace. Please refer to 49 InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html How to repeat: use sysbench ./oltp_read_write.lua to test for a long time, and restart it at running status, and start test sysbench continually, it will Assertion failure at some time.