[MDEV-7754] innodb assert "array->n_elems < array->max_elems" on a huge blob update Created: 2015-03-11 Updated: 2015-03-31 Resolved: 2015-03-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB, Storage Engine - XtraDB |
| Affects Version/s: | 10.0 |
| Fix Version/s: | 10.0.18 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Sergei Golubchik | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream | ||
| Description |
|
InnoDB and XtraDB crash on the following test case:
Note that if the blob gets larger (45000000) or innodb-log-file-size gets smaller (209M) then there is no crash, instead there's an error InnoDB: The total blob data length (44999232) is greater than 10% of the total redo log size (440401920). Please increase total redo log size. |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2015-03-13 ] |
|
2015-03-13 15:53:32 7f8920357700 InnoDB: Assertion failure in thread 140226927621888 in file sync0sync.cc line 1325 with 10.0 on commit 184f718fef0101a7559364cb97e22ee568e64c12 |
| Comment by Jan Lindström (Inactive) [ 2015-03-13 ] |
| Comment by Jan Lindström (Inactive) [ 2015-03-16 ] |
|
How important this really is, I do not follow why someone would run their database using debug build ? |
| Comment by Jan Lindström (Inactive) [ 2015-03-17 ] |
|
commit 99a2c061d7bfc181b04a0adc14ce036fab821d85 Problem was that static array was used for storing thread mutex sync levels. Does not contain test case to avoid too big memory/disk space usage |