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

galera_sr.galera_sr_kill_all_norecovery: Test failure: query 'let $_server_id= `SELECT @@server_id`' failed: 1205: Lock wait timeout exceeded

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.4.3
    • 10.4.7
    • Galera, Tests
    • OS: CentOS Linux release 7.6.1810 (Core).

    Description

      MariaDB Server: 10.4.3-MariaDB-- built from sources, commit 764429271dc94e5af08706dd0ac6fb962c15726d .
      Galera4 lib: debug built from sources, commit 9cdbeb86c330b808571b14270e6428accb899c58.

      Run:

      ./mtr galera_sr.galera_sr_kill_all_norecovery --force --max-test-fail=0 --repeat=3
      ./mtr --suite galera_sr --force --big-test --max-test-fail=0
      

      stdout.log: (the whole file is attached: 190220_galera_sr.galera_sr_kill_all_norecovery_stdout_desktop.log)

      galera_sr.galera_sr_kill_all_norecovery 'innodb' [ fail ]
       
      mysqltest: In included file "./include/kill_galera.inc": 
      included from /home/stepan/galera/git/10.4/server/mysql-test/suite/galera_sr/t/galera_sr_kill_all_norecovery.test at line 32:
      At line 4: query 'let $_server_id= `SELECT @@server_id`' failed: 1205: Lock wait timeout exceeded; try restarting transaction
      

      See also attached 190220_galera_sr.galera_sr_kill_all_norecovery.zip.

      Note: This test failed on a HDD desktop, but passed on a SSD laptop.

      Attachments

        Issue Links

          Activity

            People

              sciascid Daniele Sciascia
              stepan.patryshev Stepan Patryshev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.