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

Deadlock occurring with parallel replication and FTWRL

    XMLWordPrintable

Details

    • 10.0.22, 10.1.9-1, 10.1.9-2

    Description

      Thread 5 is locked by global read lock but FTWRL never completes and stays in waiting for commit lock; replication thread stays locked forever until FTWRL is killed

      MariaDB(db-02)[(none)]> show processlist\G
      *************************** 1. row ***************************
            Id: 3
          User: system user
          Host: 
            db: NULL
       Command: Connect
          Time: 12612
         State: Waiting for prior transaction to start commit before starting next transaction
          Info: NULL
      Progress: 0.000
      *************************** 2. row ***************************
            Id: 4
          User: system user
          Host: 
            db: NULL
       Command: Connect
          Time: 12612
         State: Waiting for prior transaction to commit
          Info: NULL
      Progress: 0.000
      *************************** 3. row ***************************
            Id: 5
          User: system user
          Host: 
            db: crypto_data
       Command: Connect
          Time: 12612
         State: Waiting for global read lock
          Info: INSERT INTO `market_orders_ok` (`label`, `marketid`, `ordertype`, `price`, `quantity`, `total`) VALU
      Progress: 0.000
      *************************** 4. row ***************************
            Id: 6
          User: system user
          Host: 
            db: NULL
       Command: Connect
          Time: 12612
         State: Waiting for prior transaction to start commit before starting next transaction
          Info: NULL
      Progress: 0.000
      *************************** 5. row ***************************
            Id: 7
          User: system user
          Host: 
            db: NULL
       Command: Connect
          Time: 1651381
         State: Waiting for master to send event
          Info: NULL
      Progress: 0.000
      *************************** 6. row ***************************
            Id: 8
          User: system user
          Host: 
            db: NULL
       Command: Connect
          Time: 13263
         State: Waiting for room in worker thread event queue
          Info: NULL
      Progress: 0.000
      *************************** 7. row ***************************
            Id: 39
          User: monitoring
          Host: localhost
            db: NULL
       Command: Sleep
          Time: 59
         State: 
          Info: NULL
      Progress: 0.000
      *************************** 8. row ***************************
            Id: 1568378
          User: tanje6acfc0c1213cfb63
          Host: localhost
            db: NULL
       Command: Sleep
          Time: 3
         State: 
          Info: NULL
      Progress: 0.000
      *************************** 9. row ***************************
            Id: 27871929
          User: backup
          Host: localhost
            db: NULL
       Command: Query
          Time: 12612
         State: Waiting for commit lock
          Info: FLUSH TABLES WITH READ LOCK
      Progress: 0.000
      *************************** 10. row ***************************
            Id: 28082858
          User: tanje6acfc0c1213cfb63
          Host: localhost
            db: NULL
       Command: Query
          Time: 0
         State: init
          Info: show processlist
      Progress: 0.000
      10 rows in set (0.00 sec)

      Attachments

        Issue Links

          Activity

            People

              knielsen Kristian Nielsen
              tanj Guillaume Lefranc
              Votes:
              0 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.