Percona XtraBackup doesn't recognize [mariadb] and [mariadb-10.0] configuration sections
Bug #1352865 reported by
Kenny Gryp
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Medium
|
Unassigned | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Triaged
|
Medium
|
Unassigned | ||
2.3 |
Triaged
|
Medium
|
Unassigned |
Bug Description
When using MariaDB, Percona XtraBackup does not properly detect the server configuration if the configuration is done in the following blocks:
[mariadb]
[mariadb-10.0]
MariaDB at this point is still backwards compatible in that it reads [mysqld] blocks.
Percona XtraBackup should also support these blocks.
(tested with version 2.2.3)
tags: | added: low-hanging-fruit |
To post a comment you must log in.
This causes the following problem file=/etc/ my.cnf. d/server. cnf --backup --target- dir=/usr/ aih/autobackup/ CTM/nxi data_home_ dir = ./ data_file_ path = ibdata1: 10M:autoextend log_group_ home_dir = ./ log_files_ in_group = 2 log_file_ size = 50331648
xtrabackup --defaults-
xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql/nxi
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
InnoDB: Error: log file ./ib_logfile0 is of different size 268435456 bytes
InnoDB: than specified in the .cnf file 50331648 bytes!
As it fails to read the mariadb section of the server.cnf
[mariadb]
innodb_ file_per_ table = 1 buffer_ pool_size = 1G log_file_ size=256M log_buffer_ size=4M packet= 1048576000 timeout= 300 handling= pool-of- threads #Enable Thread Pool connections= 3 #Allowed number of connections to use extra port
innodb_
innodb_
innodb_
max_allowed_
max_connections=300
wait_timeout=300
interactive_
thread_
thread_pool_size=20 #Recommended Thread Pool size for OLTP
extra_port=3386 #Alternate port to login if threadpool has locked up
extra_max_
Would have been good to have a note about this on the documentation page to warn of this simple configuration errror until it is resolved, it would have saved a few hours of troubleshooting