You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug #51648 DBUG_SYNC_POINT is not defined on all platforms and mtr cant pre-check that
DBUG_SYNC_POINT has at least one strong limitation that it's not defined
on all platforms. It has issues cooperating with @@debug.
All in all its functionality is superseded by DEBUG_SYNC facility and
there is no reason to maintain the old less flexible one.
Fixed with adding debug_sync_set_action() function as a facility to set up
a sync-action in the server sources code and re-writing existing simulations
(found 3) to use it.
Couple of tests have been reworked as well.
The patch offers a pattern for setting sync-points in replication threads
where the standard DEBUG_SYNC does not suffice to reach goals.
slave is going to hang in get_master_version_and_clock
23
+
slave is unblocked
24
+
SET DEBUG_SYNC='now SIGNAL signal.get_server_id';
36
25
Check network error happened here
37
26
NETWORK ERROR
27
+
set @@global.debug = "-d,'debug_lock.before_get_SERVER_ID'";
38
28
set global debug= '';
39
29
reset master;
40
30
include/stop_slave.inc
@@ -43,3 +33,4 @@ start slave;
43
33
*** must be having the replicate-same-server-id IO thread error ***
44
34
Slave_IO_Errno= 1593
45
35
Slave_IO_Error= Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).
0 commit comments