[MDEV-12030] innodb_fast_shutdown should not wait for rollback to finish Created: 2017-02-09 Updated: 2017-03-14 Resolved: 2017-03-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.0, 10.1, 10.2 |
| Fix Version/s: | 10.1.23, 10.2.5, 10.0.31 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | innodb, recovery, shutdown | ||
| Issue Links: |
|
||||||||
| Description |
|
InnoDB shutdown is effectively waiting for the rollback of recovered transactions to finish, even though the intention seems to be to only do this when a slow shutdown (innodb_fast_shutdown=0) has been requested:
Below is the output from XtraDB shutdown with innodb_fast_shutdown=2. It shows that we are indirectly waiting for the rollback somewhere later in logs_empty_and_mark_files_at_shutdown().
The above is also showing a message about page_cleaner that conflicts with the last message.
I repeated the problem on the latest development versions of 10.0.30, 10.1.22, 10.2.4. |
| Comments |
| Comment by Marko Mäkelä [ 2017-03-14 ] |
|
This was fixed as part of |