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

All queries in all databases are suspended, but the db server can be connected

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.5.13
    • N/A
    • None
    • docker image tag: mariadb:10.5
      host: centos

    Description

      Recently, we have had several instances where the database service is not responding.

      The specific situation is: all clients can still establish new connections with the database, but when any query operation is performed on any table, the query will continue forever, neither timeout nor return results.

      The attachment is the error log, this problem first appeared around 2022-12-16 8:20:00

      Do you have any clues on this issue, we are currently at a loss

      Attachments

        Activity

          Without having full stack traces of the mariadbd process during the time of the observed hangs, it is impossible to diagnose this. The InnoDB bug MDEV-29835 could match the reported symptoms, but there could be other causes as well.

          marko Marko Mäkelä added a comment - Without having full stack traces of the mariadbd process during the time of the observed hangs, it is impossible to diagnose this. The InnoDB bug MDEV-29835 could match the reported symptoms, but there could be other causes as well.
          Kuuga HaoGuo added a comment -

          At present, it is found that before these two occurrences, the Linux system time has been set. First, the time is set to 2022/12/31 23:59:00, and the time is set back after a period of time. Can this provide any information?

          Kuuga HaoGuo added a comment - At present, it is found that before these two occurrences, the Linux system time has been set. First, the time is set to 2022/12/31 23:59:00, and the time is set back after a period of time. Can this provide any information?
          Kuuga HaoGuo added a comment - - edited
          Kuuga HaoGuo added a comment - - edited marko

          We had bugs like that before, for example, MDEV-17481. So, yes, it's plausible that moving the time backwards could trigger a bug.

          serg Sergei Golubchik added a comment - We had bugs like that before, for example, MDEV-17481 . So, yes, it's plausible that moving the time backwards could trigger a bug.

          serg, thank you for pointing out MDEV-17481. In its comments I see that extra calls to os_event_set() were proposed to recover from one particular hang.

          I think that this type of hangs are impossible in MariaDB Server 10.6 thanks to MDEV-21452 replacing the old InnoDB synchronization primitives. I am reluctant to touch the thread synchronization code in old releases.

          Kuuga, sorry, I had missed the follow-ups. Have you experienced hangs related to setting the time backwards when using MariaDB Server 10.6 or later? You may want to wait for the MariaDB Server 10.6.13 release in order to get the fix of MDEV-29835.

          marko Marko Mäkelä added a comment - serg , thank you for pointing out MDEV-17481 . In its comments I see that extra calls to os_event_set() were proposed to recover from one particular hang. I think that this type of hangs are impossible in MariaDB Server 10.6 thanks to MDEV-21452 replacing the old InnoDB synchronization primitives. I am reluctant to touch the thread synchronization code in old releases. Kuuga , sorry, I had missed the follow-ups. Have you experienced hangs related to setting the time backwards when using MariaDB Server 10.6 or later? You may want to wait for the MariaDB Server 10.6.13 release in order to get the fix of MDEV-29835 .

          People

            marko Marko Mäkelä
            Kuuga HaoGuo
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.