Online log tracking restart after max untracked age violation
Split from https:/
As a result of fixing bug 1108613, the log tracking thread quits whenever the log it hasn't read yet is overwritten. Then it needs a server restart to find out the first non-overwritten LSN and resume tracking. Such overwrite is an exceptional case that also breaks crash recovery, nevertheless it is possible to improve by not depending on the server restart (which may not even happen short-term), and to resume log tracking without it.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Moved from I_S.LOG_
I am wondering if we should diagnose the maximum untracked log age violations as follows. Since these violations result in holes in an otherwise continuous tracked LSN range, save the start LSN of the current (last) uninterrupted tracking range. Include this value in the show InnoDB status output. On the maximum age violation save the last tracked LSN. When the tracking resumes again, print the hole interval to the error log. This way a DBA can diagnose when the bitmaps become partly unusable due to tracked LSN holes and can also verify the uninterruptedness by InnoDB status output.b
Work Items
Dependency tree
* Blueprints in grey have been implemented.
