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

mysqltest, Windows : improve diagnostics if server fails to shutdown

    XMLWordPrintable

Details

    Description

      MySQL commit 74726c59b7a650b948929b2839e83e26f9853d4d
      b3e655fc0c6ab75e4037409e1783122eddcc736e
      and this one : b3198c1c9ab62ea78a95909082b8cb32ba9d5f28

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26325 mysqld process hangs when stopped after executing mysql_upgrade

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Task - A task that needs to be done. MDEV-4784 merge test cases from 5.6

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9843 InnoDB hangs on startup between "InnoDB: Apply batch completed" and "rollback segment(s) are active", various tests fail sporadically in buildbot on p8-rhel6-bintar-debug

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-11370 Improvents in MTR crash or deadlock reporting

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14080 InnoDB shutdown sometimes hangs

          • Major - Major loss of function.
          • Closed

          Activity

            People

              wlad Vladislav Vaintroub
              wlad Vladislav Vaintroub
              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.