Second node cannot be added to the cluster because of the incorrect size of the innodb_log_file_size

Bug #1364339 reported by Hrvoje Matijakovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
New
Undecided
Unassigned
5.5
New
Undecided
Unassigned

Bug Description

Setting up the cluster as mentioned in the how-to (http://www.percona.com/doc/percona-xtradb-cluster/5.5/howtos/ubuntu_howto.html#ubuntu-howto) results in innobackupex error due to incorrect innodb_log_file_size on the first node.

 cat innobackup.backup.log

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

140902 11:19:02 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/etc/mysql/my.cnf;mysql_read_default_group=xtrabackup;mysql_socket=/var/run/mysqld/mysqld.sock' as 'sstuser' (using password: YES).
140902 11:19:02 innobackupex: Connected to MySQL server
IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

innobackupex: Using mysql server version 5.5.37-35.0

innobackupex: Created backup directory /tmp/tmp.DT0hC4PHJG

140902 11:19:02 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/etc/mysql/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/tmp/tmp.1iGcqbjIXb --tmpdir=/tmp/tmp.1iGcqbjIXb --extra-lsndir='/tmp/tmp.1iGcqbjIXb' --stream=xbstream
innobackupex: Waiting for ibbackup (pid=7956) to suspend
innobackupex: Suspend file '/tmp/tmp.1iGcqbjIXb/xtrabackup_suspended_2'

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
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Error: log file ./ib_logfile0 is of different size 5242880 bytes
InnoDB: than specified in the .cnf file 50331648 bytes!
innobackupex: Error: The xtrabackup child process has died at /usr//bin/innobackupex line 2672.

Current workaround is manually setting the innodb_log_file_size in my.cnf and restarting the first node.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

This is an issue with percona xtrabackup.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.