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

Port kill_one_trx fixes from 10.4 to 10.1

    XMLWordPrintable

    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

            Activity

              People

              Assignee:
              jplindst Jan Lindström
              Reporter:
              jplindst Jan Lindström
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: