2017-04-18 20:43:20 +02:00
|
|
|
/******************************************************
|
|
|
|
|
Copyright (c) 2011-2015 Percona LLC and/or its affiliates.
|
|
|
|
|
|
|
|
|
|
Declarations for xtrabackup.cc
|
|
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
|
the Free Software Foundation; version 2 of the License.
|
|
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
|
along with this program; if not, write to the Free Software
|
2019-05-11 21:19:05 +02:00
|
|
|
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA
|
2017-04-18 20:43:20 +02:00
|
|
|
|
|
|
|
|
*******************************************************/
|
|
|
|
|
|
|
|
|
|
#ifndef XB_XTRABACKUP_H
|
|
|
|
|
#define XB_XTRABACKUP_H
|
|
|
|
|
|
|
|
|
|
#include <my_getopt.h>
|
|
|
|
|
#include "datasink.h"
|
|
|
|
|
#include "xbstream.h"
|
|
|
|
|
#include "changed_page_bitmap.h"
|
2020-12-01 13:55:46 +01:00
|
|
|
#include <set>
|
2017-04-18 20:43:20 +02:00
|
|
|
|
MDEV-12548 Initial implementation of Mariabackup for MariaDB 10.2
InnoDB I/O and buffer pool interfaces and the redo log format
have been changed between MariaDB 10.1 and 10.2, and the backup
code has to be adjusted accordingly.
The code has been simplified, and many memory leaks have been fixed.
Instead of the file name xtrabackup_logfile, the file name ib_logfile0
is being used for the copy of the redo log. Unnecessary InnoDB startup and
shutdown and some unnecessary threads have been removed.
Some help was provided by Vladislav Vaintroub.
Parameters have been cleaned up and aligned with those of MariaDB 10.2.
The --dbug option has been added, so that in debug builds,
--dbug=d,ib_log can be specified to enable diagnostic messages
for processing redo log entries.
By default, innodb_doublewrite=OFF, so that --prepare works faster.
If more crash-safety for --prepare is needed, double buffering
can be enabled.
The parameter innodb_log_checksums=OFF can be used to ignore redo log
checksums in --backup.
Some messages have been cleaned up.
Unless --export is specified, Mariabackup will not deal with undo log.
The InnoDB mini-transaction redo log is not only about user-level
transactions; it is actually about mini-transactions. To avoid confusion,
call it the redo log, not transaction log.
We disable any undo log processing in --prepare.
Because MariaDB 10.2 supports indexed virtual columns, the
undo log processing would need to be able to evaluate virtual column
expressions. To reduce the amount of code dependencies, we will not
process any undo log in prepare.
This means that the --export option must be disabled for now.
This also means that the following options are redundant
and have been removed:
xtrabackup --apply-log-only
innobackupex --redo-only
In addition to disabling any undo log processing, we will disable any
further changes to data pages during --prepare, including the change
buffer merge. This means that restoring incremental backups should
reliably work even when change buffering is being used on the server.
Because of this, preparing a backup will not generate any further
redo log, and the redo log file can be safely deleted. (If the
--export option is enabled in the future, it must generate redo log
when processing undo logs and buffered changes.)
In --prepare, we cannot easily know if a partial backup was used,
especially when restoring a series of incremental backups. So, we
simply warn about any missing files, and ignore the redo log for them.
FIXME: Enable the --export option.
FIXME: Improve the handling of the MLOG_INDEX_LOAD record, and write
a test that initiates a backup while an ALGORITHM=INPLACE operation
is creating indexes or rebuilding a table. An error should be detected
when preparing the backup.
FIXME: In --incremental --prepare, xtrabackup_apply_delta() should
ensure that if FSP_SIZE is modified, the file size will be adjusted
accordingly.
2017-06-30 09:49:37 +02:00
|
|
|
struct xb_delta_info_t
|
|
|
|
|
{
|
2019-02-06 18:50:11 +01:00
|
|
|
xb_delta_info_t(ulint page_size, ulint zip_size, ulint space_id)
|
|
|
|
|
: page_size(page_size), zip_size(zip_size), space_id(space_id) {}
|
2017-04-18 20:43:20 +02:00
|
|
|
|
2019-02-06 18:50:11 +01:00
|
|
|
ulint page_size;
|
|
|
|
|
ulint zip_size;
|
|
|
|
|
ulint space_id;
|
MDEV-12548 Initial implementation of Mariabackup for MariaDB 10.2
InnoDB I/O and buffer pool interfaces and the redo log format
have been changed between MariaDB 10.1 and 10.2, and the backup
code has to be adjusted accordingly.
The code has been simplified, and many memory leaks have been fixed.
Instead of the file name xtrabackup_logfile, the file name ib_logfile0
is being used for the copy of the redo log. Unnecessary InnoDB startup and
shutdown and some unnecessary threads have been removed.
Some help was provided by Vladislav Vaintroub.
Parameters have been cleaned up and aligned with those of MariaDB 10.2.
The --dbug option has been added, so that in debug builds,
--dbug=d,ib_log can be specified to enable diagnostic messages
for processing redo log entries.
By default, innodb_doublewrite=OFF, so that --prepare works faster.
If more crash-safety for --prepare is needed, double buffering
can be enabled.
The parameter innodb_log_checksums=OFF can be used to ignore redo log
checksums in --backup.
Some messages have been cleaned up.
Unless --export is specified, Mariabackup will not deal with undo log.
The InnoDB mini-transaction redo log is not only about user-level
transactions; it is actually about mini-transactions. To avoid confusion,
call it the redo log, not transaction log.
We disable any undo log processing in --prepare.
Because MariaDB 10.2 supports indexed virtual columns, the
undo log processing would need to be able to evaluate virtual column
expressions. To reduce the amount of code dependencies, we will not
process any undo log in prepare.
This means that the --export option must be disabled for now.
This also means that the following options are redundant
and have been removed:
xtrabackup --apply-log-only
innobackupex --redo-only
In addition to disabling any undo log processing, we will disable any
further changes to data pages during --prepare, including the change
buffer merge. This means that restoring incremental backups should
reliably work even when change buffering is being used on the server.
Because of this, preparing a backup will not generate any further
redo log, and the redo log file can be safely deleted. (If the
--export option is enabled in the future, it must generate redo log
when processing undo logs and buffered changes.)
In --prepare, we cannot easily know if a partial backup was used,
especially when restoring a series of incremental backups. So, we
simply warn about any missing files, and ignore the redo log for them.
FIXME: Enable the --export option.
FIXME: Improve the handling of the MLOG_INDEX_LOAD record, and write
a test that initiates a backup while an ALGORITHM=INPLACE operation
is creating indexes or rebuilding a table. An error should be detected
when preparing the backup.
FIXME: In --incremental --prepare, xtrabackup_apply_delta() should
ensure that if FSP_SIZE is modified, the file size will be adjusted
accordingly.
2017-06-30 09:49:37 +02:00
|
|
|
};
|
2017-04-18 20:43:20 +02:00
|
|
|
|
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
The new option --log-innodb-page-corruption is introduced.
When this option is set, backup is not interrupted if innodb corrupted
page is detected. Instead it logs all found corrupted pages in
innodb_corrupted_pages file in backup directory and finishes with error.
For incremental backup corrupted pages are also copied to .delta file,
because we can't do LSN check for such pages during backup,
innodb_corrupted_pages will also be created in incremental backup
directory.
During --prepare, corrupted pages list is read from the file just after
redo log is applied, and each page from the list is checked if it is allocated
in it's tablespace or not. If it is not allocated, then it is zeroed out,
flushed to the tablespace and removed from the list. If all pages are removed
from the list, then --prepare is finished successfully and
innodb_corrupted_pages file is removed from backup directory. Otherwise
--prepare is finished with error message and innodb_corrupted_pages contains
the list of the pages, which are detected as corrupted during backup, and are
allocated in their tablespaces, what means backup directory contains corrupted
innodb pages, and backup can not be considered as consistent.
For incremental --prepare corrupted pages from .delta files are applied
to the base backup, innodb_corrupted_pages is read from both base in
incremental directories, and the same action is proceded for corrupted
pages list as for full --prepare. innodb_corrupted_pages file is
modified or removed only in base directory.
If DDL happens during backup, it is also processed at the end of backup
to have correct tablespace names in innodb_corrupted_pages.
2020-08-20 15:49:40 +02:00
|
|
|
class CorruptedPages
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
CorruptedPages();
|
|
|
|
|
~CorruptedPages();
|
2020-12-02 17:29:49 +01:00
|
|
|
void add_page(const char *file_name, ulint space_id, unsigned page_no);
|
|
|
|
|
bool contains(ulint space_id, unsigned page_no) const;
|
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
The new option --log-innodb-page-corruption is introduced.
When this option is set, backup is not interrupted if innodb corrupted
page is detected. Instead it logs all found corrupted pages in
innodb_corrupted_pages file in backup directory and finishes with error.
For incremental backup corrupted pages are also copied to .delta file,
because we can't do LSN check for such pages during backup,
innodb_corrupted_pages will also be created in incremental backup
directory.
During --prepare, corrupted pages list is read from the file just after
redo log is applied, and each page from the list is checked if it is allocated
in it's tablespace or not. If it is not allocated, then it is zeroed out,
flushed to the tablespace and removed from the list. If all pages are removed
from the list, then --prepare is finished successfully and
innodb_corrupted_pages file is removed from backup directory. Otherwise
--prepare is finished with error message and innodb_corrupted_pages contains
the list of the pages, which are detected as corrupted during backup, and are
allocated in their tablespaces, what means backup directory contains corrupted
innodb pages, and backup can not be considered as consistent.
For incremental --prepare corrupted pages from .delta files are applied
to the base backup, innodb_corrupted_pages is read from both base in
incremental directories, and the same action is proceded for corrupted
pages list as for full --prepare. innodb_corrupted_pages file is
modified or removed only in base directory.
If DDL happens during backup, it is also processed at the end of backup
to have correct tablespace names in innodb_corrupted_pages.
2020-08-20 15:49:40 +02:00
|
|
|
void drop_space(ulint space_id);
|
|
|
|
|
void rename_space(ulint space_id, const std::string &new_name);
|
|
|
|
|
bool print_to_file(const char *file_name) const;
|
|
|
|
|
void read_from_file(const char *file_name);
|
|
|
|
|
bool empty() const;
|
|
|
|
|
void zero_out_free_pages();
|
|
|
|
|
|
|
|
|
|
private:
|
2020-12-02 17:29:49 +01:00
|
|
|
void add_page_no_lock(const char *space_name, ulint space_id,
|
|
|
|
|
unsigned page_no, bool convert_space_name);
|
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
The new option --log-innodb-page-corruption is introduced.
When this option is set, backup is not interrupted if innodb corrupted
page is detected. Instead it logs all found corrupted pages in
innodb_corrupted_pages file in backup directory and finishes with error.
For incremental backup corrupted pages are also copied to .delta file,
because we can't do LSN check for such pages during backup,
innodb_corrupted_pages will also be created in incremental backup
directory.
During --prepare, corrupted pages list is read from the file just after
redo log is applied, and each page from the list is checked if it is allocated
in it's tablespace or not. If it is not allocated, then it is zeroed out,
flushed to the tablespace and removed from the list. If all pages are removed
from the list, then --prepare is finished successfully and
innodb_corrupted_pages file is removed from backup directory. Otherwise
--prepare is finished with error message and innodb_corrupted_pages contains
the list of the pages, which are detected as corrupted during backup, and are
allocated in their tablespaces, what means backup directory contains corrupted
innodb pages, and backup can not be considered as consistent.
For incremental --prepare corrupted pages from .delta files are applied
to the base backup, innodb_corrupted_pages is read from both base in
incremental directories, and the same action is proceded for corrupted
pages list as for full --prepare. innodb_corrupted_pages file is
modified or removed only in base directory.
If DDL happens during backup, it is also processed at the end of backup
to have correct tablespace names in innodb_corrupted_pages.
2020-08-20 15:49:40 +02:00
|
|
|
struct space_info_t {
|
|
|
|
|
std::string space_name;
|
2020-12-02 17:29:49 +01:00
|
|
|
std::set<unsigned> pages;
|
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
The new option --log-innodb-page-corruption is introduced.
When this option is set, backup is not interrupted if innodb corrupted
page is detected. Instead it logs all found corrupted pages in
innodb_corrupted_pages file in backup directory and finishes with error.
For incremental backup corrupted pages are also copied to .delta file,
because we can't do LSN check for such pages during backup,
innodb_corrupted_pages will also be created in incremental backup
directory.
During --prepare, corrupted pages list is read from the file just after
redo log is applied, and each page from the list is checked if it is allocated
in it's tablespace or not. If it is not allocated, then it is zeroed out,
flushed to the tablespace and removed from the list. If all pages are removed
from the list, then --prepare is finished successfully and
innodb_corrupted_pages file is removed from backup directory. Otherwise
--prepare is finished with error message and innodb_corrupted_pages contains
the list of the pages, which are detected as corrupted during backup, and are
allocated in their tablespaces, what means backup directory contains corrupted
innodb pages, and backup can not be considered as consistent.
For incremental --prepare corrupted pages from .delta files are applied
to the base backup, innodb_corrupted_pages is read from both base in
incremental directories, and the same action is proceded for corrupted
pages list as for full --prepare. innodb_corrupted_pages file is
modified or removed only in base directory.
If DDL happens during backup, it is also processed at the end of backup
to have correct tablespace names in innodb_corrupted_pages.
2020-08-20 15:49:40 +02:00
|
|
|
};
|
|
|
|
|
typedef std::map<ulint, space_info_t> container_t;
|
|
|
|
|
mutable pthread_mutex_t m_mutex;
|
|
|
|
|
container_t m_spaces;
|
|
|
|
|
};
|
|
|
|
|
|
2017-04-18 20:43:20 +02:00
|
|
|
/* value of the --incremental option */
|
|
|
|
|
extern lsn_t incremental_lsn;
|
|
|
|
|
|
|
|
|
|
extern char *xtrabackup_target_dir;
|
|
|
|
|
extern char *xtrabackup_incremental_dir;
|
|
|
|
|
extern char *xtrabackup_incremental_basedir;
|
|
|
|
|
extern char *innobase_data_home_dir;
|
|
|
|
|
extern char *innobase_buffer_pool_filename;
|
MDEV-27524: Incorrect binlogs after Galera SST using rsync and mariabackup
This commit adds correct handling of binlogs for SST using rsync
or mariabackup. Before this fix, binlogs were handled incorrectly -
- only one (last) binary log file was transferred during SST, which
then led to various failures (for example, when trying to list all
events from the binary log). These bugs were long masked by flaws
in the primitive binlogs handling code in the SST scripts, which
causing binary logs files to be erased after transfer or not added
to the binlog index on the joiner node. Now the correct transfer
of all binary logs (not just the last of the binary log files) has
been implemented both for the rsync (at the script level) and for
the mariabackup (at the level of the main utility code).
This commit also adds a new sst_max_binlogs=<n> parameter, which
can be located in the [sst] section or in the [xtrabackup] section
(historically, supported for mariabackup only, not for rsync), or
in one of the server sections. This parameter specifies the number
of binary log files to be sent to the joiner node during SST. This
option is added for compatibility with old SST scripting behavior,
which can be emulated by setting the sst_max_binlogs=1 (although
in general this can cause problems for the reasons described above).
In addition, setting the sst_max_binlogs=0 can be used to suppress
the transmission of binary logs to the joiner nodes during SST
(although sometimes a single file with the current binary log can
still be transmitted to the joiner, even with sst_max_binlogs=0,
because this sometimes necessary in modes that involve the use of
GTIDs with Galera).
Also, this commit ensures correct handling of paths to various
innodb files and directories in the SST scripts, and fixes some
problems with this that existed in mariabackup utility (which
were associated with incorrect handling of the innodb_data_dir
parameter in some scenarios).
In addition, this commit contains the following enhancements:
1) Added tests for mtr, which check the correct work with binlogs
after SST (using rsync and mariabackup);
2) Added correct handling of slashes at the end of all paths that
the SST script receives as parameters;
3) Improved parsing code for --mysqld-args parameters. Now it
correctly processes the sequence "--" after the name of the
one-letter option;
4) Checking the secret signature during joiner authentication
is made independent of presence of bash (as a unix shell)
in the system and diff utility no longer needed to check
certificates compliance;
5) All directories that are necessary for the correct placement
of various logs are automatically created by SST scripts in
advance (before running mariabackup on the joiner node);
6) Removal of old binary logs on joiner is done using the binlog
index (if it exists) (not only by fixed pattern that based
on the current binlog name, as before);
7) Paths for placing binary logs are correctly processed if they
are set as relative paths (to the datadir);
8) SST scripts are made even more resistant to spaces in filenames
(now for binlogs);
9) In case of failure, SST scripts now always end with an exit
code other than zero;
10) SST script for rsync now correctly create a tar file with
the binlogs, even if the paths to them (in the binlog index
file) are specified as a mix of absolute and relative paths,
and even if they do not match with the datadir path specified
in the current configuration settings.
2022-02-22 10:45:06 +01:00
|
|
|
extern char *buffer_pool_filename;
|
2017-08-21 19:16:12 +02:00
|
|
|
extern char *xb_plugin_dir;
|
2018-06-07 16:13:54 +02:00
|
|
|
extern char *xb_rocksdb_datadir;
|
|
|
|
|
extern my_bool xb_backup_rocksdb;
|
|
|
|
|
|
2017-08-21 19:16:12 +02:00
|
|
|
extern uint opt_protocol;
|
2017-04-18 20:43:20 +02:00
|
|
|
extern ds_ctxt_t *ds_meta;
|
|
|
|
|
extern ds_ctxt_t *ds_data;
|
|
|
|
|
|
|
|
|
|
/* The last checkpoint LSN at the backup startup time */
|
|
|
|
|
extern lsn_t checkpoint_lsn_start;
|
|
|
|
|
|
|
|
|
|
extern xb_page_bitmap *changed_page_bitmap;
|
|
|
|
|
|
|
|
|
|
extern char *xtrabackup_incremental;
|
|
|
|
|
extern my_bool xtrabackup_incremental_force_scan;
|
|
|
|
|
|
|
|
|
|
extern lsn_t metadata_to_lsn;
|
|
|
|
|
|
|
|
|
|
extern xb_stream_fmt_t xtrabackup_stream_fmt;
|
|
|
|
|
extern ibool xtrabackup_stream;
|
|
|
|
|
|
|
|
|
|
extern char *xtrabackup_tables;
|
|
|
|
|
extern char *xtrabackup_tables_file;
|
|
|
|
|
extern char *xtrabackup_databases;
|
|
|
|
|
extern char *xtrabackup_databases_file;
|
2017-04-19 15:09:03 +02:00
|
|
|
extern char *xtrabackup_tables_exclude;
|
|
|
|
|
extern char *xtrabackup_databases_exclude;
|
2017-04-18 20:43:20 +02:00
|
|
|
|
2019-01-14 22:28:23 +01:00
|
|
|
extern uint xtrabackup_compress;
|
2017-04-18 20:43:20 +02:00
|
|
|
|
|
|
|
|
extern my_bool xtrabackup_backup;
|
|
|
|
|
extern my_bool xtrabackup_prepare;
|
|
|
|
|
extern my_bool xtrabackup_copy_back;
|
|
|
|
|
extern my_bool xtrabackup_move_back;
|
|
|
|
|
extern my_bool xtrabackup_decrypt_decompress;
|
|
|
|
|
|
|
|
|
|
extern char *innobase_data_file_path;
|
|
|
|
|
extern longlong innobase_page_size;
|
|
|
|
|
|
|
|
|
|
extern int xtrabackup_parallel;
|
|
|
|
|
|
|
|
|
|
extern my_bool xb_close_files;
|
|
|
|
|
extern const char *xtrabackup_compress_alg;
|
2019-01-14 22:28:23 +01:00
|
|
|
|
|
|
|
|
extern uint xtrabackup_compress_threads;
|
|
|
|
|
extern ulonglong xtrabackup_compress_chunk_size;
|
|
|
|
|
|
2017-04-18 20:43:20 +02:00
|
|
|
extern my_bool xtrabackup_export;
|
|
|
|
|
extern char *xtrabackup_extra_lsndir;
|
|
|
|
|
extern ulint xtrabackup_log_copy_interval;
|
|
|
|
|
extern char *xtrabackup_stream_str;
|
|
|
|
|
extern long xtrabackup_throttle;
|
|
|
|
|
extern longlong xtrabackup_use_memory;
|
|
|
|
|
|
|
|
|
|
extern my_bool opt_galera_info;
|
|
|
|
|
extern my_bool opt_slave_info;
|
|
|
|
|
extern my_bool opt_no_lock;
|
|
|
|
|
extern my_bool opt_safe_slave_backup;
|
|
|
|
|
extern my_bool opt_rsync;
|
|
|
|
|
extern my_bool opt_force_non_empty_dirs;
|
|
|
|
|
extern my_bool opt_noversioncheck;
|
|
|
|
|
extern my_bool opt_no_backup_locks;
|
|
|
|
|
extern my_bool opt_decompress;
|
|
|
|
|
extern my_bool opt_remove_original;
|
2018-12-20 14:31:18 +01:00
|
|
|
extern my_bool opt_extended_validation;
|
2019-01-23 13:00:12 +01:00
|
|
|
extern my_bool opt_encrypted_backup;
|
2018-03-30 00:13:01 +02:00
|
|
|
extern my_bool opt_lock_ddl_per_table;
|
MDEV-22929 MariaBackup option to report and/or continue when corruption is encountered
The new option --log-innodb-page-corruption is introduced.
When this option is set, backup is not interrupted if innodb corrupted
page is detected. Instead it logs all found corrupted pages in
innodb_corrupted_pages file in backup directory and finishes with error.
For incremental backup corrupted pages are also copied to .delta file,
because we can't do LSN check for such pages during backup,
innodb_corrupted_pages will also be created in incremental backup
directory.
During --prepare, corrupted pages list is read from the file just after
redo log is applied, and each page from the list is checked if it is allocated
in it's tablespace or not. If it is not allocated, then it is zeroed out,
flushed to the tablespace and removed from the list. If all pages are removed
from the list, then --prepare is finished successfully and
innodb_corrupted_pages file is removed from backup directory. Otherwise
--prepare is finished with error message and innodb_corrupted_pages contains
the list of the pages, which are detected as corrupted during backup, and are
allocated in their tablespaces, what means backup directory contains corrupted
innodb pages, and backup can not be considered as consistent.
For incremental --prepare corrupted pages from .delta files are applied
to the base backup, innodb_corrupted_pages is read from both base in
incremental directories, and the same action is proceded for corrupted
pages list as for full --prepare. innodb_corrupted_pages file is
modified or removed only in base directory.
If DDL happens during backup, it is also processed at the end of backup
to have correct tablespace names in innodb_corrupted_pages.
2020-08-20 15:49:40 +02:00
|
|
|
extern my_bool opt_log_innodb_page_corruption;
|
2017-04-18 20:43:20 +02:00
|
|
|
|
|
|
|
|
extern char *opt_incremental_history_name;
|
|
|
|
|
extern char *opt_incremental_history_uuid;
|
|
|
|
|
|
|
|
|
|
extern char *opt_user;
|
2021-02-05 13:57:46 +01:00
|
|
|
extern const char *opt_password;
|
2017-04-18 20:43:20 +02:00
|
|
|
extern char *opt_host;
|
|
|
|
|
extern char *opt_defaults_group;
|
|
|
|
|
extern char *opt_socket;
|
|
|
|
|
extern uint opt_port;
|
|
|
|
|
extern char *opt_log_bin;
|
|
|
|
|
|
|
|
|
|
extern const char *query_type_names[];
|
|
|
|
|
|
|
|
|
|
enum query_type_t {QUERY_TYPE_ALL, QUERY_TYPE_UPDATE,
|
|
|
|
|
QUERY_TYPE_SELECT};
|
|
|
|
|
|
|
|
|
|
extern TYPELIB query_type_typelib;
|
|
|
|
|
|
|
|
|
|
extern ulong opt_lock_wait_query_type;
|
|
|
|
|
extern ulong opt_kill_long_query_type;
|
|
|
|
|
|
|
|
|
|
extern uint opt_kill_long_queries_timeout;
|
|
|
|
|
extern uint opt_lock_wait_timeout;
|
|
|
|
|
extern uint opt_lock_wait_threshold;
|
|
|
|
|
extern uint opt_debug_sleep_before_unlock;
|
|
|
|
|
extern uint opt_safe_slave_backup_timeout;
|
MDEV-27524: Incorrect binlogs after Galera SST using rsync and mariabackup
This commit adds correct handling of binlogs for SST using rsync
or mariabackup. Before this fix, binlogs were handled incorrectly -
- only one (last) binary log file was transferred during SST, which
then led to various failures (for example, when trying to list all
events from the binary log). These bugs were long masked by flaws
in the primitive binlogs handling code in the SST scripts, which
causing binary logs files to be erased after transfer or not added
to the binlog index on the joiner node. Now the correct transfer
of all binary logs (not just the last of the binary log files) has
been implemented both for the rsync (at the script level) and for
the mariabackup (at the level of the main utility code).
This commit also adds a new sst_max_binlogs=<n> parameter, which
can be located in the [sst] section or in the [xtrabackup] section
(historically, supported for mariabackup only, not for rsync), or
in one of the server sections. This parameter specifies the number
of binary log files to be sent to the joiner node during SST. This
option is added for compatibility with old SST scripting behavior,
which can be emulated by setting the sst_max_binlogs=1 (although
in general this can cause problems for the reasons described above).
In addition, setting the sst_max_binlogs=0 can be used to suppress
the transmission of binary logs to the joiner nodes during SST
(although sometimes a single file with the current binary log can
still be transmitted to the joiner, even with sst_max_binlogs=0,
because this sometimes necessary in modes that involve the use of
GTIDs with Galera).
Also, this commit ensures correct handling of paths to various
innodb files and directories in the SST scripts, and fixes some
problems with this that existed in mariabackup utility (which
were associated with incorrect handling of the innodb_data_dir
parameter in some scenarios).
In addition, this commit contains the following enhancements:
1) Added tests for mtr, which check the correct work with binlogs
after SST (using rsync and mariabackup);
2) Added correct handling of slashes at the end of all paths that
the SST script receives as parameters;
3) Improved parsing code for --mysqld-args parameters. Now it
correctly processes the sequence "--" after the name of the
one-letter option;
4) Checking the secret signature during joiner authentication
is made independent of presence of bash (as a unix shell)
in the system and diff utility no longer needed to check
certificates compliance;
5) All directories that are necessary for the correct placement
of various logs are automatically created by SST scripts in
advance (before running mariabackup on the joiner node);
6) Removal of old binary logs on joiner is done using the binlog
index (if it exists) (not only by fixed pattern that based
on the current binlog name, as before);
7) Paths for placing binary logs are correctly processed if they
are set as relative paths (to the datadir);
8) SST scripts are made even more resistant to spaces in filenames
(now for binlogs);
9) In case of failure, SST scripts now always end with an exit
code other than zero;
10) SST script for rsync now correctly create a tar file with
the binlogs, even if the paths to them (in the binlog index
file) are specified as a mix of absolute and relative paths,
and even if they do not match with the datadir path specified
in the current configuration settings.
2022-02-22 10:45:06 +01:00
|
|
|
extern uint opt_max_binlogs;
|
2017-04-18 20:43:20 +02:00
|
|
|
|
|
|
|
|
extern const char *opt_history;
|
|
|
|
|
|
2019-03-14 16:59:27 +01:00
|
|
|
enum binlog_info_enum { BINLOG_INFO_OFF, BINLOG_INFO_ON,
|
2017-04-18 20:43:20 +02:00
|
|
|
BINLOG_INFO_AUTO};
|
|
|
|
|
|
|
|
|
|
extern ulong opt_binlog_info;
|
|
|
|
|
|
2021-04-01 11:33:59 +02:00
|
|
|
extern ulong xtrabackup_innodb_force_recovery;
|
|
|
|
|
|
2017-04-18 20:43:20 +02:00
|
|
|
void xtrabackup_io_throttling(void);
|
|
|
|
|
my_bool xb_write_delta_metadata(const char *filename,
|
|
|
|
|
const xb_delta_info_t *info);
|
|
|
|
|
|
|
|
|
|
/************************************************************************
|
|
|
|
|
Checks if a table specified as a name in the form "database/name" (InnoDB 5.6)
|
|
|
|
|
or "./database/name.ibd" (InnoDB 5.5-) should be skipped from backup based on
|
|
|
|
|
the --tables or --tables-file options.
|
|
|
|
|
|
|
|
|
|
@return TRUE if the table should be skipped. */
|
|
|
|
|
my_bool
|
|
|
|
|
check_if_skip_table(
|
|
|
|
|
/******************/
|
|
|
|
|
const char* name); /*!< in: path to the table */
|
|
|
|
|
|
2017-04-19 15:09:03 +02:00
|
|
|
|
|
|
|
|
/************************************************************************
|
|
|
|
|
Checks if a database specified by path should be skipped from backup based on
|
|
|
|
|
the --databases, --databases_file or --databases_exclude options.
|
|
|
|
|
|
|
|
|
|
@return TRUE if the table should be skipped. */
|
|
|
|
|
my_bool
|
|
|
|
|
check_if_skip_database_by_path(
|
|
|
|
|
const char* path /*!< in: path to the db directory. */
|
|
|
|
|
);
|
|
|
|
|
|
2017-04-18 20:43:20 +02:00
|
|
|
/************************************************************************
|
|
|
|
|
Check if parameter is set in defaults file or via command line argument
|
|
|
|
|
@return true if parameter is set. */
|
|
|
|
|
bool
|
|
|
|
|
check_if_param_set(const char *param);
|
|
|
|
|
|
2017-04-18 21:05:57 +02:00
|
|
|
#if defined(HAVE_OPENSSL)
|
|
|
|
|
extern my_bool opt_ssl_verify_server_cert;
|
|
|
|
|
#endif
|
|
|
|
|
|
2017-04-18 20:43:20 +02:00
|
|
|
|
|
|
|
|
my_bool
|
|
|
|
|
xb_get_one_option(int optid,
|
|
|
|
|
const struct my_option *opt __attribute__((unused)),
|
|
|
|
|
char *argument);
|
|
|
|
|
|
|
|
|
|
const char*
|
|
|
|
|
xb_get_copy_action(const char *dflt = "Copying");
|
|
|
|
|
|
2017-09-11 18:45:36 +02:00
|
|
|
void mdl_lock_init();
|
|
|
|
|
void mdl_lock_table(ulint space_id);
|
|
|
|
|
void mdl_unlock_all();
|
2017-09-13 14:10:48 +02:00
|
|
|
bool ends_with(const char *str, const char *suffix);
|
2020-04-20 16:23:43 +02:00
|
|
|
|
|
|
|
|
typedef void (*insert_entry_func_t)(const char*);
|
|
|
|
|
|
|
|
|
|
/* Scan string and load filter entries from it.
|
|
|
|
|
@param[in] list string representing a list
|
|
|
|
|
@param[in] delimiters delimiters of entries
|
|
|
|
|
@param[in] ins callback to add entry */
|
|
|
|
|
void xb_load_list_string(char *list, const char *delimiters,
|
|
|
|
|
insert_entry_func_t ins);
|
|
|
|
|
void register_ignore_db_dirs_filter(const char *name);
|
2021-05-18 11:13:18 +02:00
|
|
|
|
|
|
|
|
#ifdef _WIN32
|
|
|
|
|
typedef HANDLE os_file_dir_t; /*!< directory stream */
|
|
|
|
|
/** The os_file_opendir() function opens a directory stream corresponding to the
|
|
|
|
|
directory named by the dirname argument. The directory stream is positioned
|
|
|
|
|
at the first entry. In both Unix and Windows we automatically skip the '.'
|
|
|
|
|
and '..' items at the start of the directory listing.
|
|
|
|
|
|
|
|
|
|
@param[in] dirname directory name; it must not contain a trailing
|
|
|
|
|
'\' or '/'
|
|
|
|
|
@return directory stream
|
|
|
|
|
@retval INVALID_HANDLE_VALUE on error */
|
|
|
|
|
HANDLE os_file_opendir(const char *dirname);
|
|
|
|
|
# define os_file_closedir(dir) static_cast<void>(FindClose(dir))
|
|
|
|
|
# define os_file_closedir_failed(dir) !FindClose(dir)
|
|
|
|
|
#else
|
|
|
|
|
typedef DIR* os_file_dir_t;
|
|
|
|
|
# define os_file_opendir(dirname) opendir(dirname)
|
|
|
|
|
# define os_file_closedir(dir) static_cast<void>(closedir(dir))
|
|
|
|
|
# define os_file_closedir_failed(dir) closedir(dir)
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/** This function returns information of the next file in the directory. We jump
|
|
|
|
|
over the '.' and '..' entries in the directory.
|
|
|
|
|
@param[in] dirname directory name or path
|
|
|
|
|
@param[in] dir directory stream
|
|
|
|
|
@param[out] info buffer where the info is returned
|
|
|
|
|
@return 0 if ok, -1 if error, 1 if at the end of the directory */
|
|
|
|
|
int
|
|
|
|
|
os_file_readdir_next_file(
|
|
|
|
|
const char* dirname,
|
|
|
|
|
os_file_dir_t dir,
|
|
|
|
|
os_file_stat_t* info);
|
|
|
|
|
|
|
|
|
|
/***********************************************************************//**
|
|
|
|
|
A fault-tolerant function that tries to read the next file name in the
|
|
|
|
|
directory. We retry 100 times if os_file_readdir_next_file() returns -1. The
|
|
|
|
|
idea is to read as much good data as we can and jump over bad data.
|
|
|
|
|
@return 0 if ok, -1 if error even after the retries, 1 if at the end
|
|
|
|
|
of the directory */
|
|
|
|
|
int
|
|
|
|
|
fil_file_readdir_next_file(
|
|
|
|
|
/*=======================*/
|
|
|
|
|
dberr_t* err, /*!< out: this is set to DB_ERROR if an error
|
|
|
|
|
was encountered, otherwise not changed */
|
|
|
|
|
const char* dirname,/*!< in: directory name or path */
|
|
|
|
|
os_file_dir_t dir, /*!< in: directory stream */
|
|
|
|
|
os_file_stat_t* info); /*!< in/out: buffer where the
|
|
|
|
|
info is returned */
|
2017-04-18 20:43:20 +02:00
|
|
|
#endif /* XB_XTRABACKUP_H */
|