| Bug #38312 | main.backup_ddl_blocker fails sporadically | ||
|---|---|---|---|
| Submitted: | 23 Jul 2008 12:45 | Modified: | 26 Nov 2008 20:48 |
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | 6.0-BK | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | pushbuild, sporadic, test failure | ||
[26 Nov 2008 20:48]
Ingo Strüwing
This is most probably a duplicate of Bug#39152 (Intermittent debug_sync time-outs in backup tests). There were several sporadic failures due to improper mutex protection in the debug_sync code. The fix for Bug#39152 has been pushed to main on 2008-09-20. The above xref link shows that backup_ddl_blocker didn't fail any more after that. The failures in mysql-6.0-ndb on 2008-10-17 are not sporadic failures, but a different problem. OTOH backup_ddl_blocker has been disabled on 2008-10-09 and still is. If the problem re-appears after it is re-enabled, please reset the status to "verified".
Description: @@ -649,10 +649,13 @@ debug sync point: after_start_ddl DROP TABLE bup_ddl_blocker.t2 con6: Resume all and wait for restore to start after DDL finish. SET DEBUG_SYNC= 'now SIGNAL status_shown WAIT_FOR bup_started'; +Warnings: +Warning 1720 debug sync point wait timed out SELECT state, info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE info LIKE "RESTORE FROM%"; state info -debug sync point: after_block_ddl RESTORE FROM "bup_ddl_blocker_orig.bak" +Warnings: +Warning 1366 Incorrect string value: '\x8F\x8F\x8F\x8F\x8F\x8F...' for column 'INFO' at row 1 con4: Activate synchronization point for DDL. SET DEBUG_SYNC= 'before_check_ddl_blocked SIGNAL con4_started WAIT_FOR status_shown2'; How to repeat: https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=&testtyp...