Not the answer you need?
Register and ask your own question!

Xtrabackup broken with MariaDB Galera Cluster

chstehlchstehl EntrantCurrent User Role Beginner
Hi there,

with the update to XtraBackup 2.3, the SST-Method xtrabackup-v2 is not working anymore with our MariaDB Galera Cluster 10.
Also Innobackupex is terminating with errors. After rollback to xtrabackup 2.2 everything runs fine again.
Is there a solution for this available?
MariaDB Galera Server 10.0.21 on centos7, WSREP Provider 25.3.9(r3387)

Christian

Comments

  • DenisDenis Entrant Current User Role Beginner
    I also failed to use xtrabackup (2.3.2 ) to join a new node to a galera cluster( Server version: 10.0.21-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4144) with xtrabackup-v2 method. after I switch to the 2.2.13 version, no problem. When i check the donor log:
    151216 6:33:58 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.74.3.195:4444/xtrabackup_sst' --auth 'sst_user:
    xxxx' --socket '/home/mysql/db02/admin/mysql.sock' --datadir '/home/mysql/db02/data/' --defaults-file '/home/mysql/galera-10.0.21/my.cnf
    ' --defaults-group-suffix '' --binlog '/home/mysql/db02/binlogs/mysql_db02-bin' --gtid '5d57dce4-a28c-11e5-b74c-9a364e95fd0d:9''
    151216 6:33:58 [Note] WSREP: sst_donor_thread signaled with 0
    WSREP_SST: [INFO] Streaming with xbstream (20151216 06:33:59.093)
    WSREP_SST: [INFO] Using socat as streamer (20151216 06:33:59.095)
    WSREP_SST: [INFO] Using /tmp/tmp.tXBdi22845 as innobackupex temporary directory (20151216 06:33:59.105)
    WSREP_SST: [INFO] Streaming GTID file before SST (20151216 06:33:59.108)
    WSREP_SST: [INFO] Streaming the backup to joiner at 10.74.3.195 4444 (20151216 06:34:09.119)
    WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/home/mysql/galera-10.0.21/my.cnf --defaults-group=mysqld --no-version-check $tmp
    opts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.74.3.195:4444; RC=( ${PIPESTAT
    US[@]} ) (20151216 06:34:09.121)
    151216 6:34:11 [Note] WSREP: Provider paused at 5d57dce4-a28c-11e5-b74c-9a364e95fd0d:9 (15)
    151216 6:34:11 [Note] WSREP: resuming provider at 15
    151216 6:34:11 [Note] WSREP: Provider resumed.
    WSREP_SST: [ERROR] innobackupex finished with error: 1. Check /home/mysql/db02/data//innobackup.backup.log (20151216 06:34:11.522)
    WSREP_SST: [ERROR] Cleanup after exit with status:22 (20151216 06:34:11.524)

    when i check /home/mysql/db02/data//innobackup.backup.log, it has:

    [00] error: cannot open file /home/mysql/db02/data//mysql_db02-bin.000003

    While the file mysql_db02-bin.000003 is actually at /home/mysql/db02/binlogs/ . It looks to me in the 2.3 version , the default location of binlog used, even with --binlog '/home/mysql/db02/binlogs/mysql_db02-bin used in wsrep_sst_xtrabackup-v2



    Denis
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.