[MDEV-24026] InnoDB: Failing assertion: os_total_large_mem_allocated >= size upon incremental backup Created: 2020-10-26 Updated: 2023-05-18 Resolved: 2020-10-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | mariabackup, Storage Engine - InnoDB |
| Affects Version/s: | 10.2 |
| Fix Version/s: | 10.2.35, 10.3.26, 10.4.16, 10.5.7 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Elena Stepanova | Assignee: | Vladislav Lesin |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | regression, rr-profile | ||
| Issue Links: |
|
||||||||
| Description |
|
Failure happens upon incremental backup. There are no obvious errors in the backup log prior to the failure. rr profile is available. The problem apparently appeared in 10.2 after this commit:
The test I use to reproduce the failure (happens frequently enough on the recent 10.2, every other run or so):
|
| Comments |
| Comment by Vladislav Lesin [ 2020-10-28 ] | |||||||||||||||||||||||
|
The reason of the bug is the following:
I.e. write_filt_ctxt.u.wf_incremental_ctxt is not initialized, and it's deallocated in the case if some table was dropped during backup, and the corresponding DDL redo log record was read and parsed. This is indeed not a regression, because previous commits did not touch the sequence of local variables initialization in xtrabackup_copy_datafile(). | |||||||||||||||||||||||
| Comment by Igor Yagolnitser [ 2023-05-11 ] | |||||||||||||||||||||||
|
If you are backporting |