Changes between Version 88 and Version 89 of Replication_Issues

Timestamp:

Mar 29, 2019, 9:48:34 AM (7 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -15 +15 @@
 Fix:
 The issue was with so_id = 6604319651 which didn't (and still doesn't) exist in ippdb01.
+
 When attempting to execute the statement:
+{{{
 # at 1040640772
 #190328 17:56:35 server id 2017081601  end_log_pos 1040641174 CRC32 0xb21142d6  Update_rows: table id 73 flags: STMT_END_F
@@ -21 +23 @@
 [...]
 # at 1040641174
-replication stopped since row with so_id=6604319651 didn't exist.
+}}}
+
+The replication stopped since row with so_id=6604319651 didn't exist.
 
 In db09 a few hours after the crash:
+{{{
 mysql> SELECT * FROM storage_object WHERE so_id = 6604319651;
 Empty set (0.00 sec)
-So I assumed that so_id = 6604319651 would be deleted at some point in the replicant future. It is:
+}}}
+
+I assumed that so_id = 6604319651 would be deleted at some point in the replicant future. It is:
+
+{{{
 # at 1040669677
 #190328 17:56:35 server id 2017081601  end_log_pos 1040669911 CRC32 0x131ec7a0  Delete_rows: table id 73 flags: STMT_END_F
@@ -32 +41 @@
 [...]
 # at 1040669911
+}}}
 
 So...