Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5, 10.0, 10.1, 10.2.3, 10.2.4, 10.2.5, 10.3.0, 10.2.6
Description
When a slow shutdown is performed soon after creating some activity for fts_optimize_thread(), it is possible that the optimize thread is starting new transactions after the purge has finished. This is violating the specification of innodb_fast_shutdown, namely that the purge must be completed. (None of the history of new transactions would be purged.)
The proper fix would seem to declare a flag that indicates whether undo-log-generating background threads are active:
/** Shut down background threads that can generate undo log. */
|
void
|
srv_shutdown_bg_undo_sources()
|
{
|
if (srv_bg_undo_sources) {
|
ut_ad(!srv_read_only_mode);
|
fts_optimize_shutdown();
|
dict_stats_shutdown();
|
srv_bg_undo_sources = false;
|
}
|
}
|
As long as this flag is set, srv_purge_should_exit() must return false.
Attachments
Issue Links
- is caused by
-
MDEV-5800 indexes on virtual (not materialized) columns
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-