[MDEV-12323] Rollback progress log messages during crash recovery are intermixed with unrelated log messages Created: 2017-03-21 Updated: 2020-08-25 Resolved: 2017-12-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.20 |
| Fix Version/s: | 10.0.34, 10.1.30, 10.2.12, 10.3.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | innodb, rollback | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
When InnoDB rolls back uncommitted transactions during crash recovery, it writes messages to the error log to keep track of its progress. However, these messages can be intermixed with unrelated error log messages. Consider the following log snippet:
The progress reporting starts with the following message:
And then the following message is intermixed on the same line:
And you can see the same happening when the following progress report message is written:
And then the following shutdown log message is intermixed on the same line:
After the shutdown request, the progress report messages become even harder to pick out, as each one is mixed in with its own message about waiting on active transactions. Here's the progress report for 14%:
And 15%:
We should probably change how these progress report messages are printed, so that they aren't intermixed with unrelated log messages. |
| Comments |
| Comment by Marko Mäkelä [ 2017-12-13 ] |
|
The messages will be displayed every 15 seconds, just like the crash recovery messages that were introduced in |