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

Shutdown of database and stop slave do not work in MariaDB 10.3.17 when slave threads are running

Details

    Description

      Hi,

      I just upgraded a slave of a 10.3.15 from 10.3.15 to 10.3.17. Now I cannot shutdown the database or stop the slave threads, if they are running (I need to use kill -9).

      When I start the database with skip_slave_start, I can shutdown the database normally.
      When I start only the IO_THREAD or only the SQL_THREAD, stop slave works.
      When I start all threads, neither stopping them or shutting down the whole database works.
      However, when the master is not reachable when starting the slave threads, stopping them is possible.
      When the master is shut down while the slave threads are running, stopping the threads will not work. show slave status shows:

      Slave_SQL_Running_State: Waiting for worker threads to be idle
      

      Please let me know if you need further information.

      Cheers,
      Volker

      Attachments

        Issue Links

          Activity

            elenst Elena Stepanova added a comment - - edited

            It could be related to MDEV-20247.
            Do you use any non-zero value of innodb-thread-concurrency? Try to disable it and see if the problem goes away.
            Also, if you get a readable stack trace of all threads from the hanging slave, we'll probably be able to tell with more certainty. But if you indeed use the value and disabling it helps, with all likelihood it's the same problem.

            elenst Elena Stepanova added a comment - - edited It could be related to MDEV-20247 . Do you use any non-zero value of innodb-thread-concurrency ? Try to disable it and see if the problem goes away. Also, if you get a readable stack trace of all threads from the hanging slave, we'll probably be able to tell with more certainty. But if you indeed use the value and disabling it helps, with all likelihood it's the same problem.
            vklasen Volker Klasen added a comment -

            Yes, I do have innodb-thread-concurrency set to 64 and the issue goes away once I set it to 0. So, I guess, this is a duplicate of MDEV-20247.
            As I can't provide a stack trace (without much effort), I propose to close this as duplicate and I'll wait for 10.3.18 to check again.

            Thanks,
            Volker

            vklasen Volker Klasen added a comment - Yes, I do have innodb-thread-concurrency set to 64 and the issue goes away once I set it to 0. So, I guess, this is a duplicate of MDEV-20247 . As I can't provide a stack trace (without much effort), I propose to close this as duplicate and I'll wait for 10.3.18 to check again. Thanks, Volker

            Thanks for the update.

            elenst Elena Stepanova added a comment - Thanks for the update.

            Should be fixed in the scope of MDEV-20247.

            elenst Elena Stepanova added a comment - Should be fixed in the scope of MDEV-20247 .

            People

              Unassigned Unassigned
              vklasen Volker Klasen
              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.