Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.13, 10.5.3, 10.2(EOL), 10.3(EOL)
-
None
Description
Workflow
|
1. A session connects and creates the table t1 and inserts one record.
|
CREATE TABLE t1 (col1 INT, col2 INT, col3 INT, col4 TEXT) ENGINE = InnoDB ;
|
ALTER TABLE t1 ADD PRIMARY KEY ( col4(10), col2 ) ;
|
INSERT INTO t1 (col2,col4) VALUES(2, 'Sooo inportant data');
|
Mode is auto commit.
|
2. The same session runs random
|
ALTER TABLE t1 FORCE or
|
ALTER TABLE t1 ADD COLUMN extra INT; ALTER TABLE t1 DROP COLUMN col3 ; ALTER TABLE t1 CHANGE COLUMN extra col3 INT ;
|
3. At some point of time the server process gets killed (SIGKILL).
|
4. The server gets restartet.
|
5. Now
|
SHOW KEYS FROM `test`.`t1` harvests (~ 1 case on 50 runs)
|
1932: Table 'test.t1' doesn't exist in engine.
|
6. RQG kills the server process with SIGKILL because of 5.
|
|
|
origin/10.4 cfbbf5424bc68a31a996ab42a253f2c96365599c 2020-04-29T11:50:03+03:00
|
no matter if compiled with debug or not
|
|
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
{noformat} Workflow 1. A session connects and creates the table t1 and inserts one record. CREATE TABLE t1 (col1 INT, col2 INT, col3 INT, col4 TEXT) ENGINE = InnoDB ; ALTER TABLE t1 ADD PRIMARY KEY ( col4(10), col2 ) ; INSERT INTO t1 (col2,col4) VALUES(2, 'Sooo inportant data'); Mode is auto commit. 2. The same session runs random ALTER TABLE t1 FORCE or ALTER TABLE t1 ADD COLUMN extra INT; ALTER TABLE t1 DROP COLUMN col3 ; ALTER TABLE t1 CHANGE COLUMN extra col3 INT ; 3. At some point of time the server process gets killed (SIGKILL). 4. The server gets restartet. 5. Now SHOW KEYS FROM `test`.`t1` harvests 1932: Table 'test.t1' doesn't exist in engine. {noformat} |
{noformat}
Workflow 1. A session connects and creates the table t1 and inserts one record. CREATE TABLE t1 (col1 INT, col2 INT, col3 INT, col4 TEXT) ENGINE = InnoDB ; ALTER TABLE t1 ADD PRIMARY KEY ( col4(10), col2 ) ; INSERT INTO t1 (col2,col4) VALUES(2, 'Sooo inportant data'); Mode is auto commit. 2. The same session runs random ALTER TABLE t1 FORCE or ALTER TABLE t1 ADD COLUMN extra INT; ALTER TABLE t1 DROP COLUMN col3 ; ALTER TABLE t1 CHANGE COLUMN extra col3 INT ; 3. At some point of time the server process gets killed (SIGKILL). 4. The server gets restartet. 5. Now SHOW KEYS FROM `test`.`t1` harvests (~ 1 case on 50 runs) 1932: Table 'test.t1' doesn't exist in engine. origin/10.4 cfbbf5424bc68a31a996ab42a253f2c96365599c 2020-04-29T11:50:03+03:00 no matter if compiled with debug or not {noformat} |
| Description |
{noformat}
Workflow 1. A session connects and creates the table t1 and inserts one record. CREATE TABLE t1 (col1 INT, col2 INT, col3 INT, col4 TEXT) ENGINE = InnoDB ; ALTER TABLE t1 ADD PRIMARY KEY ( col4(10), col2 ) ; INSERT INTO t1 (col2,col4) VALUES(2, 'Sooo inportant data'); Mode is auto commit. 2. The same session runs random ALTER TABLE t1 FORCE or ALTER TABLE t1 ADD COLUMN extra INT; ALTER TABLE t1 DROP COLUMN col3 ; ALTER TABLE t1 CHANGE COLUMN extra col3 INT ; 3. At some point of time the server process gets killed (SIGKILL). 4. The server gets restartet. 5. Now SHOW KEYS FROM `test`.`t1` harvests (~ 1 case on 50 runs) 1932: Table 'test.t1' doesn't exist in engine. origin/10.4 cfbbf5424bc68a31a996ab42a253f2c96365599c 2020-04-29T11:50:03+03:00 no matter if compiled with debug or not {noformat} |
{noformat}
Workflow 1. A session connects and creates the table t1 and inserts one record. CREATE TABLE t1 (col1 INT, col2 INT, col3 INT, col4 TEXT) ENGINE = InnoDB ; ALTER TABLE t1 ADD PRIMARY KEY ( col4(10), col2 ) ; INSERT INTO t1 (col2,col4) VALUES(2, 'Sooo inportant data'); Mode is auto commit. 2. The same session runs random ALTER TABLE t1 FORCE or ALTER TABLE t1 ADD COLUMN extra INT; ALTER TABLE t1 DROP COLUMN col3 ; ALTER TABLE t1 CHANGE COLUMN extra col3 INT ; 3. At some point of time the server process gets killed (SIGKILL). 4. The server gets restartet. 5. Now SHOW KEYS FROM `test`.`t1` harvests (~ 1 case on 50 runs) 1932: Table 'test.t1' doesn't exist in engine. 6. RQG kills the server process with SIGKILL because of 5. origin/10.4 cfbbf5424bc68a31a996ab42a253f2c96365599c 2020-04-29T11:50:03+03:00 no matter if compiled with debug or not {noformat} |
| Attachment | 000047.log [ 51508 ] |
| Assignee | Matthias Leich [ mleich ] | Thirunarayanan Balathandayuthapani [ thiru ] |
| Summary | Draft: 1932: Table 'test.t1' doesn't exist in engine after crash recovery | 1932: Table 'test.t1' doesn't exist in engine after crash recovery |
| Attachment | mdev-22140.patch [ 51568 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
matthias.leich mentioned that "Now I get either a pass (even before the majority of runs harvested a pass) or "Table 't1' is marked as crashed and should be repaired". IMHO better"
| Summary | 1932: Table 'test.t1' doesn't exist in engine after crash recovery | Change the error when table schema mismatch |
| Summary | Change the error when table schema mismatch | Change the error when table schema mismatch happens |
| Fix Version/s | 10.4.13 [ 24223 ] | |
| Fix Version/s | 10.5.3 [ 24263 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 107962 ] | MariaDB v4 [ 157694 ] |
This issue looks like design flaw. It would be fixed by
MDEV-17567. However, InnoDB can give better error compared to "Table doesn't exist".The following patch does that:
mdev-22140.patch