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

Add option for SQL thread to kill any blocking local activity

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • N/A
    • Replication
    • None

    Description

      DDL executed on primary may be blocked by any long running SELECT on replica, thus breaking the "high availability" of this setup. It seems there is no way even to force limited wait time for DDL on replica.

      Please, add server variable to force priority for SQL thread in such cases, similar to what happens in Galera.

      UPDATE:
      from MDEV-29569, which is the same request, but has one additional information:
      "Proper logging options (similar to those we have in Galera) should also be added, to help understand the reason of error local connection to slave may get."

      Attachments

        Issue Links

          is duplicated by

          Task - A task that needs to be done. MDEV-29569 Add option for SQL thread to terminate all transactions and statements that block it

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34857 Implement --slave-abort-blocking-timeout

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              knielsen Kristian Nielsen
              valerii Valerii Kravchuk
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.