Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
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.
MDEV-16421 - Make system tables crash safe
Attachments
Issue Links
- relates to
-
MDEV-17912
Aria with encryption fails upon crash recovery: Redo phase failed, "Got error 192"
-
- Stalled
-
-
MDEV-17913 Encrypted transactional Aria tables remain corrupt after crash recovery, automatic repairment does not work
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| 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|https://travis-ci.org/elenst/travis-tests/branches] regularly (daily at first, weekly after GA) along with other various tests. |
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|https://travis-ci.org/elenst/travis-tests/branches] regularly (daily at first, weekly after GA) along with other various tests. |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
CrashRestart reporter didn't work well, switched to CrashUpgrade scenario (same basedir), adjusted configuration, added runs with encryption and group commit.
| Link | This issue relates to MDEV-17912 [ MDEV-17912 ] |
| Link |
This issue relates to |
Tests are being run regularly and are mostly saturated due to the amount of existing bugs (see MDEV-19813 for more details).
| Fix Version/s | N/A [ 14700 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 90966 ] | MariaDB v4 [ 133774 ] |
Added a first small set of tests:
- --grammar=conf/mariadb/oltp-transactional.yy --gendata=conf/mariadb/oltp-aria.zz- --grammar=conf/mariadb/oltp.yy --gendata=conf/mariadb/oltp-aria.zz- --grammar=conf/mariadb/generic-dml.yy --gendata=conf/mariadb/oltp-aria.zz- --grammar=conf/engines/engine_stress.yy --gendata=conf/engines/engine_stress.zz --engine=Ariaeach in 3 variations:
- as is- --gendata-advanced --vcols --default-storage-engine=Aria- --mysqld=--log_bin_trust_function_creators=1 --mysqld=--log-binall with CrashRestart reporter.
Also need to add encrypted version.