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

Port kill_one_trx fixes from 10.4 to 10.1

Details

    Description

      There following issues here:

      • Whenever Galera BF (brute force) transaction decides to abort conflicting transaction it will kill that thread using thd::awake()
      • Whenever replication selects a thread as a victim it will call thd::awake()
      • User KILL [QUERY|CONNECTION] ... for a thread it will also call thd::awake()

      Whenever one of these actions is executed we will hold number of InnoDB internal mutexes and thd mutexes.
      Sometimes these mutexes are taken in different order causing mutex deadlock (see one detailed case below).

      Refs

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-12009 Allow to force kill user threads/query which are flagged as high priority by Galera

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17063 server locks up and is killed after innodb_fatal_semaphore_wait_threshold is reached

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19803 Long semaphore wait error on galera.MW-388

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23328 Server hang due to Galera lock conflict resolution

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18874 Galera test MW-286 causes Mutex = TTASEventMutex<GenericPolicy>]: Assertion `!is_owned()' failed. assertion

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21910 KIlling thread on Galera could cause mutex deadlock

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23851 Galera assertion at lock0lock.cc line 655 because of BF-BF lock wait

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

          Activity

            Transition Time In Source Status Execution Times
            Jan Lindström (Inactive) made transition -
            Open In Progress
            		17s 1
            Marko Mäkelä made transition -
            In Review Stalled
            		44d 22h 44m 2
            Jan Lindström (Inactive) made transition -
            In Progress Closed
            		22h 29m 1
            Marko Mäkelä made transition -
            Closed Stalled
            		3h 52m 1
            Jan Lindström (Inactive) made transition -
            In Progress Stalled
            		163d 23h 40m 1
            Jan Lindström (Inactive) made transition -
            Stalled In Progress
            		5d 15h 54m 4
            Jan Lindström (Inactive) made transition -
            In Progress In Review
            		130d 7h 56m 3
            Jan Lindström (Inactive) made transition -
            In Review Closed
            		54d 21h 44m 1

            People

              jplindst Jan Lindström (Inactive)
              jplindst Jan Lindström (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              9 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.