Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6457

preserve slave_skip_errors binlog events to own binlog

Details

    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.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-6458 feature request - galera failed certifications to own binlog

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Task - A task that needs to be done. MDEV-7198 [PATCH] status variable for Slave_skipped_errors

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            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.

            elenst Elena Stepanova added a comment - 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.
            danblack Daniel Black added a comment -

            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).

            danblack Daniel Black added a comment - 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).
            danblack Daniel Black added a comment -

            a status variable slave_skip_errors_count would also be good for monitoring/graphing

            danblack Daniel Black added a comment - a status variable slave_skip_errors_count would also be good for monitoring/graphing

            People

              knielsen Kristian Nielsen
              danblack Daniel Black
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.