[MDEV-6457] preserve slave_skip_errors binlog events to own binlog Created: 2014-07-18 Updated: 2015-10-29 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Daniel Black | Assignee: | Kristian Nielsen |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | binlog, replication, slave | ||
| Issue Links: |
|
||||||||||||
| Description |
|
When slave_skip_errors has a setting, its useful to know which events got triggered. Is a slave_skip_errors_binlog possible to store events in blog format that for the slave_skip_errors criteria are skipped? This would assist with post-mortem, what when wrong as well as provide a recovery mechanism. |
| Comments |
| Comment by Elena Stepanova [ 2014-07-18 ] |
|
I vote for that. Don't know about a separate binlog, maybe it's hard to implement, but at least they could be written in the error log, in the same form as they would have been written if there were no slave_skip_errors, only as warnings instead of errors. |
| Comment by Daniel Black [ 2014-07-21 ] |
|
As warnings in the error log is good also. At least with a binlog you don't have the same consistency obligations of a normal binlog. The case I had in mind was using for was bulk loading 10K row insert statements and some failed on primary key (possibly the client did something odd before I was engaged). |
| Comment by Daniel Black [ 2014-07-21 ] |
|
a status variable slave_skip_errors_count would also be good for monitoring/graphing |