Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
In a similar theme to MDEV-6457, can galera certification failures that show up (indecipherably) is the log (as follows), end up in their own binlog to assist debugging the part of the user application(s) that caused the transaction and to assist recovery if that's what's needed.
Jul 14 09:40:57 db-prod-iin-galera1 mysqld: 140714 9:40:57 [Note] WSREP: trx conflict for key (1,FLAT8)65ff9f39 e8c2fa20: source: f734dbd4-03ad-11e4-adb0-67819bed06e8 version: 3 local: 0 state: CERTIFYING flags: 1 conn_id: 317902 trx_id: 60435815 seqnos (l: 1682417, g: 21956902, s: 21956885, d: 21956734, ts: 794238915267495) <--X--> source: 535a24cb-03ae-11e4-a429-4723cd38bd9a version: 3 local: 1 state: COMMITTED flags: 1 conn_id: 475341 trx_id: 65728464 seqnos (l: 1682409, g: 21956894, s: 21956886, d: 21956734, ts: 794117838622465)
|
Attachments
Issue Links
- relates to
-
MDEV-6457 preserve slave_skip_errors binlog events to own binlog
- Open