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

ROW format ignores slave-skip-errors = all

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Critical
        • Resolution: Incomplete
        • Affects Version/s: 5.5.37
        • Fix Version/s: N/A
        • Component/s: None
        • Labels:
          None
        • Environment:
          CentOS 6.x

          Description

          When slave-skip-errors = all and format is set to ROW, errors block replication.

            Gliffy Diagrams

              Attachments

                Activity

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

                Hi Alexey,

                Could you please provide more information – what you are running on master, which errors happen on the slave, and how they block replication?
                I tried ER_TABLE_EXISTS_ERROR, it seems to be skipped all right.

                Show
                elenst Elena Stepanova added a comment - Hi Alexey, Could you please provide more information – what you are running on master, which errors happen on the slave, and how they block replication? I tried ER_TABLE_EXISTS_ERROR, it seems to be skipped all right.
                Hide
                Permalink
                elenst Elena Stepanova added a comment -

                Please comment to re-open if you have more information.

                Show
                elenst Elena Stepanova added a comment - Please comment to re-open if you have more information.
                Hide
                Permalink
                elenst Elena Stepanova added a comment -

                While searching for something else, I found this entry MDEV-3525 which might be related to the initial problem (depending on what the scenario really was).

                Show
                elenst Elena Stepanova added a comment - While searching for something else, I found this entry MDEV-3525 which might be related to the initial problem (depending on what the scenario really was).

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    azilber Alexey Zilber
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    3 Start watching this issue

                    Dates

                    • Due:
                      Created:
                      Updated:
                      Resolved: