Bug #115059 | record in index not found on update | ||
---|---|---|---|
Submitted: | 20 May 2024 9:10 | Modified: | 20 May 2024 9:56 |
Reporter: | yangyang wang | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Linux |
Assigned to: | CPU Architecture: | x86 |
[20 May 2024 9:10]
yangyang wang
[20 May 2024 9:11]
yangyang wang
we found a issue from mariadb https://jira.mariadb.org/browse/MDEV-22986 bug not sure
[20 May 2024 9:56]
MySQL Verification Team
HI MR. wang, Thank you for your bug report. However, let us inform you that this is a forum for the bugs with repeatable test cases. Each test case should consist of a set of SQL statements leading to the bug that is reported. We do not see such a test case in your report. Also, regarding putting a server under high load, you can use either sysbench, or much better mysqlslap program. We do not use any third party utilities. It is also very important for you to know that we are testing test cases on the installation with full ACID setup. Hence, killing MySQL under such a setup will not lead to any loss of data, including loss of index entries. We have run many stress tests and our fully ACID stood up to the tests. Hence, in vast majority of cases, our ACID setup stood well and did not lead to any losses. Can't repeat.