Incorrect handling of FTS optimize thread in xtrabackup_56
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Invalid
|
Undecided
|
Unassigned |
Bug Description
xtrabackup_56 implements an incorrect logic with respect to the FTS optimize thread and --apply-log-only.
The thread is always started on XtraBackup recovery innobase_
if (!srv_read_
/* Shutdown the FTS optimize sub system. */
fts_optimize_
fts_optimize_
}
The code in fts_optimize_
Related branches
- Alexey Kopytov (community): Needs Fixing
-
Diff: 19 lines (+0/-9)1 file modifiedpatches/innodb56.patch (+0/-9)
- Alexey Kopytov (community): Needs Fixing
-
Diff: 19 lines (+0/-9)1 file modifiedpatches/innodb56.patch (+0/-9)
tags: | added: archived-logs |
Actually FTS optimize thread is started not always. It is not started if srv_archive_ recovery is off. See the following code in innobase_ start_or_ create_ for_mysql( ):
if (srv_apply_ log_only) {
goto skip_processes;
}
So this is "apply archived logs" specific bug because it does not skip fts initialization.