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

Shutdown hangs after upgrade to 10.5.12

    XMLWordPrintable

Details

    Description

      Shutdown hangs after upgrade to 10.5.12

      Shutdown hangs was reported on some sites after upgrade to 10.5.12 (from 10.5.10).
      This is semisync replication. Master was started and running while 2 slaves hang on shutdown (done with innodb_fast_shutdown=0)
      Configuration parameters are same between those site that work and does not.
      Backtraces are attached here.

      I am trying to get more details, but according to initial report some nodes work without problems, while other hangs (for days).

      Some of parameters are:

      MemTotal: 32471016 kB(30.97G)

      innodb_buffer_pool_size 4294967296 (4GB)
      tmp_table_size 16777216 (16MB) <--I asked bump up to 134217728 (128MB). But it was rejected since "worked before upgrade"
      Max_used_connections 32

      innodb_autoinc_lock_mode 1
      innodb_flush_log_at_timeout 1

      Attachments

        1. mysqld_full_bt_all_threads-node1.txt
          83 kB
          Yakov Kushnirsky
        2. mysqld_full_bt_all_threads-node2.txt
          62 kB
          Yakov Kushnirsky
        3. mysqld_full_bt_all_threads-node2-1.txt
          61 kB
          Yakov Kushnirsky
        4. mysqld_full_bt_all_threads-node2-2.txt
          61 kB
          Yakov Kushnirsky
        5. ssq-3-2021-10-15-09-56.saas.appiancloud.com-20211019-mysqld_bt_all_threads.txt
          66 kB
          Yakov Kushnirsky

        Issue Links

          Activity

            People

              Unassigned Unassigned
              YK Yakov Kushnirsky
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.