With log messages like the following is there a sane way to parse this back into something useful like a database, table and/or row? If so can it be done by galera instead of me?
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)
If it can't be made sense of can I ask for a feature request that galera write the binlog data from this to its own log.
--
Daniel Black, Engineer @ Open Query (
http://openquery.com.au)
Remote expertise & maintenance for MySQL/MariaDB server environments.