Changes between Version 89 and Version 90 of Replication_Issues

Timestamp:

Mar 29, 2019, 9:53:09 AM (7 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -7 +7 @@
 == 2019-03-29 09:30 ==
 
-Issue: Replication crashed on ippdb01 replicating ippdb09.
+=== Issue ===
+Replication crashed on ippdb01 replicating ippdb09.
 {{{
                    Last_Errno: 1032
@@ -13 +14 @@
 }}}
 
-Fix:
-The issue was with so_id = 6604319651 which didn't (and still doesn't) exist in ippdb01.
+=== Fix ===
+==== Short story ====
+The issue was with so_id = 6604319651 which didn't (and still doesn't) exist in ippdb01 and a statement trying to update that row. I couldn't identify why 6604319651 was deleted but it's easy to mess up with replication.
+
+==== Gory details ====
+Full statements in /export/ippdb01.0/mysql/archives/dump-20190329.txt
 
 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
-... UPDATE nebulous`.`storage_object` WHERE so_id=6604319651
+#190328 17:56:35 server id 2017081601  end_log_pos 1040641174 [...]
+### UPDATE nebulous`.`storage_object` WHERE so_id=6604319651
 [...]
 # at 1040641174
@@ -37 +42 @@
 {{{
 # at 1040669677
-#190328 17:56:35 server id 2017081601  end_log_pos 1040669911 CRC32 0x131ec7a0  Delete_rows: table id 73 flags: STMT_END_F
+#190328 17:56:35 server id 2017081601  end_log_pos 1040669911 [...]
 ### DELETE FROM `nebulous`.`storage_object` WHERE so_id=6604319651
 [...]