Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.13, 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-1049-aws x86_64) running on Amazon AWS EC2 (Can provide instance level if needed)
Description
On a production server, we experience a crash during an alter table. I have attached the relevant entries from syslog (which is where MariaDB logs to), along with a similar SQL creation statement for the table that was altered. Unfortunately, the table in question was marked as crashed after the service restarted, and there was multiple entries per second being written to the error log about the table being crashed. Another member of the development team made the decision to drop the original table, and we don't have a backup of that table (it is a new table, being used as a summary table).
The main known difference between the attached SQL for the table and the original is that the original had Foreign Keys to other tables. If you feel this might be relevant, I can attempt to find the foreign keys that were in place, along with the table definitions of those the target tables.
MDEV-14021 has a similar crash (same assertion fail), so setting as relates to (I don't know enough about this bug to say if it is the same or not).
Attachments
Issue Links
- duplicates
-
MDEV-16060 InnoDB: Failing assertion: ut_strcmp(index->name, key->name)
- Closed
-
MDEV-17552 [Draft] Assertion `user_table->get_ref_count() == 1' failed in commit_try_rebuild
- Closed
- relates to
-
MDEV-14021 Failing assertion: table->get_ref_count() == 0 on ALTER TABLE with implicit ALGORITHM=INPLACE
- Closed
-
MDEV-18062 Assertion `index' failed in ha_innobase::innobase_get_index or locking issues upon concurrent operations with foreign keys
- Closed
-
MDEV-19539 Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.15/storage/innobase/row/row0merge.cc line 4509
- Closed