[MDEV-17864] Run regular crash recovery tests for Aria tables (system and user tables) Created: 2018-11-28 Updated: 2019-07-07 Resolved: 2019-07-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Tests |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Critical |
| Reporter: | Elena Stepanova | Assignee: | Elena Stepanova |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
We have crash recovery tests, but those mainly target InnoDB. Aria is only involved in 10.4 to the extent that the server with Aria system tables starts after the crash. We'll run similar tests but with Aria tables instead of InnoDB. Data creation needs to be adjusted, pre-crash DML can remain basically the same, after-recovery checks might need to be adjusted, post-crash DML/DDL can remain the same. The tests are to be run in Travis regularly (daily at first, weekly after GA) along with other various tests.
|
| Comments |
| Comment by Elena Stepanova [ 2018-11-30 ] | |||||||
|
Added a first small set of tests:
each in 3 variations:
all with CrashRestart reporter. Also need to add encrypted version. | |||||||
| Comment by Elena Stepanova [ 2018-11-30 ] | |||||||
|
CrashRestart reporter didn't work well, switched to CrashUpgrade scenario (same basedir), adjusted configuration, added runs with encryption and group commit. | |||||||
| Comment by Elena Stepanova [ 2019-07-07 ] | |||||||
|
Tests are being run regularly and are mostly saturated due to the amount of existing bugs (see MDEV-19813 for more details). |