Comment 2 for bug 1337919

Revision history for this message
Michel Tougas (mtougas) wrote :

I no longer have the logs from the original test but I just ran it again and here it is. I just post the end of the log file because there are a lot of "log scanned up to ..." logs. So I guess there is a timeout somewhere? Can it be adjusted depending on the bandwidth between the nodes in the cluster?

...
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
>> log scanned up to (31106649839)
DBD::mysql::db selectall_hashref failed: Lock wait timeout exceeded; try restarting transaction at /usr/local/mariadb/5.5.37//bin/innobackupex line 2996.
innobackupex: Error:
Error executing 'SHOW STATUS': DBD::mysql::db selectall_hashref failed: Lock wait timeout exceeded; try restarting transaction at /usr/local/mariadb/5.5.37//bin/innobackupex line 2996.
140707 15:37:25 innobackupex: Waiting for ibbackup (pid=27803) to finish

The JOINER logs show that it failed after ~ 14 minutes 30 seconds.

WSREP_SST: [INFO] Evaluating nc -dl 4444 | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20140707 15:23:06.252)
140707 15:35:04 [Note] WSREP: Created page /var/broadworks/persistent/gcache.page.000000 of size 134217728 bytes
WSREP_SST: [ERROR] xtrabackup process ended without creating '/var/broadworks/persistent//xtrabackup_galera_info' (20140707 15:37:31.607)