[MDEV-6458] feature request - galera failed certifications to own binlog Created: 2014-07-18  Updated: 2019-12-14

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Daniel Black Assignee: Ralf Gebhardt
Resolution: Unresolved Votes: 0
Labels: binlog, galera

Issue Links:
Relates
relates to MDEV-6457 preserve slave_skip_errors binlog eve... Open

 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)



 Comments   
Comment by Daniel Black [ 2014-07-21 ]

As Alexey mentioned ( https://groups.google.com/d/msg/codership-team/W36rfiF-JpM/CZgwmPdYfFIJ ) the repl.key_format=*A will assist. He's also keen on something more informative.

Generated at Thu Feb 08 07:12:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.