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

MariaRocks: [ERROR] mysqld: Deadlock found when trying to get lock messages in server stderr

Details

    Description

      A number of tests started to fail recently like this:

      ./mtr rocksdb.locking_issues
      ....
      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      rocksdb.locking_issues                   [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-03-16 19:50:00
      line
      2017-03-16 19:47:40 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
      2017-03-16 19:48:58 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
      2017-03-16 19:49:38 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
      ^ Found warnings in /home/psergey/dev-git/10.2-mariarocks/mysql-test/var/log/mysqld.1.err
      ok
      

      Attachments

        Issue Links

          Activity

            psergei Sergei Petrunia created issue -
            psergei Sergei Petrunia made changes -
            Field Original Value New Value
            psergei Sergei Petrunia made changes -
            Description A number of tests started to fail recently like this:

            {noformat}
            ./mtr rocksdb.locking_issues
            Logging: ./mtr rocksdb.locking_issues
            vardir: /home/psergey/dev-git/10.2-mariarocks/mysql-test/var
            Removing old var directory...
             - WARNING: Using the 'mysql-test/var' symlink
            Creating var directory '/home/psergey/dev-git/10.2-mariarocks/mysql-test/var'...
            Checking supported features...
             MariaDB Version 10.2.5-MariaDB-debug
             - SSL connections supported
             - binaries are debug compiled
            Collecting tests...
            Installing system database...

            ==============================================================================

            TEST RESULT TIME (ms) or COMMENT
            --------------------------------------------------------------------------

            worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
            rocksdb.locking_issues [ fail ] Found warnings/errors in server log file!
                    Test ended at 2017-03-16 19:50:00
            line
            2017-03-16 19:47:40 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            2017-03-16 19:48:58 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            2017-03-16 19:49:38 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            ^ Found warnings in /home/psergey/dev-git/10.2-mariarocks/mysql-test/var/log/mysqld.1.err
            ok
            {noformat}
            A number of tests started to fail recently like this:

            {noformat}
            ./mtr rocksdb.locking_issues
            ....
            worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
            rocksdb.locking_issues [ fail ] Found warnings/errors in server log file!
                    Test ended at 2017-03-16 19:50:00
            line
            2017-03-16 19:47:40 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            2017-03-16 19:48:58 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            2017-03-16 19:49:38 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
            ^ Found warnings in /home/psergey/dev-git/10.2-mariarocks/mysql-test/var/log/mysqld.1.err
            ok
            {noformat}
            psergei Sergei Petrunia added a comment - - edited

            The warnings are now visible, because log_warnings=2 after this change:
            https://github.com/MariaDB/server/commit/3435e8a51552c3c73feab4b1c731dd8da225618c

            If I take an older server and put

            set log_warnings=2;
            set global log_warnings=2;
            

            at the top of locking_issues.test, I get the same warnings.

            psergei Sergei Petrunia added a comment - - edited The warnings are now visible, because log_warnings=2 after this change: https://github.com/MariaDB/server/commit/3435e8a51552c3c73feab4b1c731dd8da225618c If I take an older server and put set log_warnings=2; set global log_warnings=2; at the top of locking_issues.test, I get the same warnings.

            Disabled the warnings in bb-10.2-mariarocks tree

            psergei Sergei Petrunia added a comment - Disabled the warnings in bb-10.2-mariarocks tree
            psergei Sergei Petrunia made changes -
            Fix Version/s N/A [ 14700 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 80011 ] MariaDB v4 [ 133181 ]

            People

              Unassigned Unassigned
              psergei Sergei Petrunia
              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.