| Bug #100148 | During a parallel read operation, the rollback of a table load operation causes | ||
|---|---|---|---|
| Submitted: | 8 Jul 2020 3:07 | Modified: | 10 Aug 2020 12:22 |
| Reporter: | shangshang yu | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 8.0.18 | OS: | Red Hat |
| Assigned to: | CPU Architecture: | x86 | |
[8 Jul 2020 3:07]
shangshang yu
[8 Jul 2020 3:07]
shangshang yu
innodb status show the lock info: OS WAIT ARRAY INFO: reservation count 3114 --Thread 140070095931136 has waited at row0pread.cc line 245 for 254 seconds the semaphore: S-lock on RW-latch at 0x7f738ea7c2e8 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode exclusive number of readers 0, waiters flag 1, lock_word: 0 Last time read locked in file row0row.cc line 919 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/include/mtr0mtr.ic line 142 --Thread 140133994104576 has waited at row0ins.cc line 2446 for 254 seconds the semaphore: S-lock on RW-latch at 0x7f738ea7c2e8 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode exclusive number of readers 0, waiters flag 1, lock_word: 0 Last time read locked in file row0row.cc line 919 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/include/mtr0mtr.ic line 142 --Thread 140070112716544 has waited at row0pread.cc line 245 for 248 seconds the semaphore: S-lock on RW-latch at 0x7f738ea7c2e8 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode exclusive number of readers 0, waiters flag 1, lock_word: 0 Last time read locked in file row0row.cc line 919 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/include/mtr0mtr.ic line 142 --Thread 140070121109248 has waited at row0pread.cc line 245 for 253 seconds the semaphore: S-lock on RW-latch at 0x7f738ea7c2e8 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode exclusive number of readers 0, waiters flag 1, lock_word: 0 Last time read locked in file row0row.cc line 919 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/include/mtr0mtr.ic line 142 --Thread 140134135555840 has waited at btr0cur.cc line 233 for 254 seconds the semaphore: X-lock (wait_ex) on RW-latch at 0x7f6ce14fc018 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode wait exclusive number of readers 1, waiters flag 0, lock_word: ffffffffffffffff Last time read locked in file row0pread.cc line 336 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/btr/btr0cur.cc line 233 --Thread 140070104323840 has waited at row0pread.cc line 245 for 254 seconds the semaphore: S-lock on RW-latch at 0x7f738ea7c2e8 created in file buf0buf.cc line 777 a writer (thread id 140134135555840) has reserved it in mode exclusive number of readers 0, waiters flag 1, lock_word: 0 Last time read locked in file row0row.cc line 919 Last time write locked in file /ci/taurus-root/src/sql/storage/innobase/include/mtr0mtr.ic line 142
[8 Jul 2020 13:39]
MySQL Verification Team
Hi Mr. yu, Thank you for your bug report. However, in order to verify it , we must be able to repeat it. Hence, we need a repeatable test case, which will always lead to this assert. Let me point out that this is not a crash, but controlled assert. This is due to the long semaphore wait, which is expected behaviour. Also, we need it repeated on the latest release of our 8.0 server.
[9 Jul 2020 3:41]
shangshang yu
The scene is same as following bug, I think their have relations. SHA-1: 48f2c0b55de952705c7fbcf308c2b6bf613223c4 * Bug#30060690 MYSQLD CRASH AFTER LOADING DATA Issue ===== During parallel read, if the entire load table is rolled back when autocommit = 0 we hit an assertion. Fix === The assertion is bogus as the point that the existing tree structure could be changed during parallel read wasn't considered. RB: 22847 Reviewed-by: Sunny Bains <sunny.bains@oracle.com> Change-Id: I3b2a23a0fe0b398b254a76b3f60b284731d170fc
[9 Jul 2020 12:00]
MySQL Verification Team
Hi Mr. yu, If you think that it is a duplicate, then I will mark him as such. Otherwise, we need a full test case. We leave it up to you .....
[10 Aug 2020 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".
