Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.34-galera
-
None
-
None
Description
I have a script that inserts 10 records into a table on Node 1. Immediately after, I run an update on Node 2 on those inserted records. I run 100 of these transactions. The intention here is to test and monitor replication conflicts.
[2014-02-01 12:37:50] 50: [WARNING] Updated didn't matched the inserted! Inserted: 10, Updated: 9
|
[2014-02-01 12:37:50] 55: [WARNING] Updated didn't matched the inserted! Inserted: 10, Updated: 9
|
[2014-02-01 12:37:50] 78: [WARNING] Updated didn't matched the inserted! Inserted: 10, Updated: 9
|
[2014-02-01 12:37:50] 79: [WARNING] Updated didn't matched the inserted! Inserted: 10, Updated: 9
|
[2014-02-01 12:37:51] 92: [WARNING] Updated didn't matched the inserted! Inserted: 10, Updated: 9
|
|
|
Node 2 Status Before: After: Change:
|
wsrep_local_bf_aborts 155 159 4
|
The "50" before WARNING is the transaction number. So the above log (from a custom script) shows five errors where the UPDATE only found 9 rows out of 10 to update. If two consecutive transactions generated a wsrep_local_bf_aborts, it seems like the status number doesn't get updated.
Attachments
Issue Links
- relates to
-
-
- Closed
-