Issue with --safe-slave-backup option in 2.4.4

Bug #1624473 reported by Michael Shield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.3
Fix Released
High
Sergei Glushchenko
2.4
Fix Released
High
Sergei Glushchenko

Bug Description

Hi,

The --safe-slave-option does not correctly operating its 3 sec time delay for re-tries.

Running an incremental backup this morning it failed while checking open tmp tables. Checking the log showed the 100 attempts with a 3 sec interval had only taken 1 sec in total. See below.

Mike

160916 08:22:06 Slave open temp tables: 1
160916 08:22:06 Starting slave SQL thread, waiting 3 seconds, then checking Slave_open_temp_tables again (99 attempts remaining)...
...
160916 08:22:06 Slave open temp tables: 1
160916 08:22:07 Starting slave SQL thread, waiting 3 seconds, then checking Slave_open_temp_tables again (0 attempts remaining)...
160916 08:22:07 Slave open temp tables: 1
160916 08:22:07 Restarting slave SQL thread.
160916 08:22:07 Slave_open_temp_tables did not become zero after 300 seconds

Unsurprisingly, the backup failed, though a re-run was OK

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-484

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.