[#MDEV-23119] ERROR 1932 Table doesn't exist in engine

error log
2020-07-07 9:36:25 1931387 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:36:32 1932374 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:38:54 1933520 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:38:54 1933520 [ERROR] Slave SQL: Error executing row event: 'Table 'fms.business' doesn't exist in engine', Gtid 0-1000-1177584, Internal MariaDB error code: 1932
2020-07-07 9:38:54 1933520 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'maria-bin.000013' position 439591739; GTID position '0-1000-1177583'
2020-07-07 9:41:33 1934785 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:46:33 1937184 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:51:33 1939583 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata
2020-07-07 9:56:33 1941982 [ERROR] InnoDB: Table `fms`.`business` contains unrecognizable instant ALTER metadata

MariaDB [fms]> show tables;

+-------------------+

| Tables_in_fms     |

+-------------------+

| business          |

+-------------------+

MariaDB [fms]> select * from business;

ERROR 1932 (42S02): Table 'fms.business' doesn't exist in engine

Currently, MariaDB 10.4.8 version is in use, and there is a problem that the table cannot be viewed.
I am afraid that this will happen again.

1. In what cases does the phenomenon occur?
2. Is this a bug?
3. How can I prevent it? Is it possible to fix it with a version upgrade?

[MDEV-23119] ERROR 1932 Table doesn't exist in engine Created: 2020-07-08 Updated: 2020-09-06 Resolved: 2020-09-06
Status:	Closed
Project:	MariaDB Server
Component/s:	Storage Engine - InnoDB
Affects Version/s:	10.4.8
Fix Version/s:	N/A