[MDEV-23508] Unexpected corruption error ER_NOT_KEYFILE upon ALTER TABLE with a certain combination of data volume and max_sort_file_size Created: 2020-08-18 Updated: 2023-08-24 Resolved: 2023-08-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Aria, Storage Engine - MyISAM |
| Affects Version/s: | 10.1, 10.2, 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Michael Widenius |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | not-10.4, not-10.5 | ||
| Description |
|
I am setting it to Minor, despite it being a corruption-looking error, because it is only reproducible on 10.1-10.3, apparently something has fixed it in 10.4+. Besides, it requires a non-default value of myisam_max_sort_file_size / aria_max_sort_file_size.
There is indeed a duplicate key in the table, but it should be error 1062 - ER_DUP_ENTRY, not 1034 - ER_NOT_KEYFILE. The printed duplicate key value is also wrong, possibly related to MDEV-23507. The problem seems to be scalable, myisam_max_sort_file_size value required to reproduce it depends on the data volume. Also reproducible with Aria:
|
| Comments |
| Comment by Elena Stepanova [ 2023-08-24 ] |
|
10.3 is EOL |