[MDEV-32798] innodb_fast_shutdown=0 hang after incomplete startup Created: 2023-11-14 Updated: 2023-11-14 Resolved: 2023-11-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.5, 10.6, 10.10, 10.11, 11.0, 11.1, 11.2, 11.3 |
| Fix Version/s: | 10.5.24, 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3, 11.3.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression | ||
| Description |
|
The following invocation will hang, because a recovered incomplete transaction exists but was not rolled back due to the fault injection innodb_log_abort_1:
The following patch fixes the hang on 10.5:
The flag srv_was_started implies trx_sys.is_initialised(), because innodb_init() would only assign that flag after a successful srv_start(), which includes initializing the transaction subsystem. MariaDB Server 10.4 is not affected by this. |
| Comments |
| Comment by Marko Mäkelä [ 2023-11-14 ] | |||||||||||||
|
The following patch that additionally checks innodb_force_recovery fixes also the tests innodb.read_only_recovery innodb.read_only_recover_committed mariabackup.apply-log-only-incr innodb.innodb_force_recovery:
|