[MDEV-14066] [Draft] Assertion failed: rec_get_deleted_flag(rec, dict_table_is_comp(cursor->index->table)) Created: 2017-10-14 Updated: 2021-11-03 Resolved: 2021-11-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Elena Stepanova |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/644/steps/crash_tests/logs/stdio
Not reproducible easily |
| Comments |
| Comment by Marko Mäkelä [ 2018-04-07 ] | ||||||||||||||||
|
The delete-mark mismatch is something that I would associate with the upstream bug that is reported as | ||||||||||||||||
| Comment by Aleksey Midenkov [ 2021-07-12 ] | ||||||||||||||||
|
bb-10.6-midenok-MDEV-18706 reproduces similar failure via rollback:
| ||||||||||||||||
| Comment by Marko Mäkelä [ 2021-09-29 ] | ||||||||||||||||
|
Failures in locking-related development branches could be due to some changes that break locking. This assertion is only reporting an inconsistency that must have been caused earlier during the execution. The culprit is always somewhere else. In particular, during the time any ROLLBACK is executed (even a rollback of a single row), the transaction must already hold exclusive locks on the records that it is deleting or updating. If that is not the case due to some ‘locking optimization’, then it could happen that another transaction may modify the record before rollback is executed. In such a case, I would expect the DB_TRX_ID of the clustered index record not to match the trx_t::id. |