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

In parallel replication, an error is not correctly signalled to the next transaction

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.0.9
    • 10.0.10
    • None
    • None

    Description

      When a transaction fails during replication, it should signal the error to any
      following transactions that are executing in parallel. However, the logic was
      incorrect, so this only worked if the error occured during the COMMIT/XID
      event at the end of the group. On other errors, following transactions would
      not be signalled correctly and would not roll back, resulting in corrupt state
      of replication.

      This bug is also seen as one of the problems in MDEV-5863.

      Many thanks to nanyi607rao for reporting this problem on maria-developer@ and
      analysing the cause.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-5863 "Lock wait timeout exceeded", lost events, Assertion `!table || !table->in_use || ta ble->in_use == _current_thd()' failure upon parallel replicating

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            knielsen Kristian Nielsen created issue -
            knielsen Kristian Nielsen made changes -
            Field Original Value New Value
            Description When a transaction fails during replication, it should signal the error to any
            following transactions that are executing in parallel. However, the logic was
            incorrect, so this only worked if the error occured during the COMMIT/XID
            event at the end of the group. On other errors, following transactions would
            not be signalled correctly and would not roll back, resulting in corrupt state
            of replication.

            Many thanks to nanyi607rao for reporting this problem on maria-developer@ and
            analysing the cause.
            		 When a transaction fails during replication, it should signal the error to any
            following transactions that are executing in parallel. However, the logic was
            incorrect, so this only worked if the error occured during the COMMIT/XID
            event at the end of the group. On other errors, following transactions would
            not be signalled correctly and would not roll back, resulting in corrupt state
            of replication.

            This bug is also seen as one of the problems in MDEV-5863.

            Many thanks to nanyi607rao for reporting this problem on maria-developer@ and
            analysing the cause.
            knielsen Kristian Nielsen made changes -
            knielsen Kristian Nielsen made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            knielsen Kristian Nielsen made changes -
            Fix Version/s 10.0.10 [ 14500 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow defaullt [ 36947 ] MariaDB v2 [ 43311 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Workflow MariaDB v2 [ 43311 ] MariaDB v3 [ 62401 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 62401 ] MariaDB v4 [ 147678 ]

            People

              knielsen Kristian Nielsen
              knielsen Kristian Nielsen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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