[MDEV-29984] innodb_fast_shutdown=0 fails to report change buffer merge progress Created: 2022-11-09 Updated: 2023-11-30 Resolved: 2022-11-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.5, 10.6, 10.7, 10.8, 10.9, 10.10 |
| Fix Version/s: | 10.11.2, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Ralf Gebhardt | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
We should get the change buffer merge process reported in the log In the same way as it was done in Currently, with innodb_fast_shutdown=0, the change buffer merge can take some time, a user might think that the server hans on shutdown as there are no updates in the server log file. |
| Comments |
| Comment by Marko Mäkelä [ 2022-11-14 ] | |||||||
|
There actually is some progress reporting for the change buffer merge, once per 60 seconds, implemented in the function srv_shutdown_print_master_pending(). But those messages were not present in the log extract that was posted in In any case, it does make sense to reduce the reporting interval from 60 to 15 seconds, to be consistent with | |||||||
| Comment by Marko Mäkelä [ 2022-11-14 ] | |||||||
|
The revised progress report will look like this:
This is from a modified test innodb.ibuf_not_empty, actually reproducing a shutdown hang that is basically the same as |