Details

    Description

      We have previously seen the server_audit plugin cause threads to hang in various states due to the problems described by MDEV-18661 / MDEV-19291. These threads could hang in many different states, such as "System lock", "init", and "freeing items." This made the root cause of the issue quite difficult to diagnose on production systems.

      In case a similar issue happens again, it might make sense to add a new "Auditing" thread state. This new thread state could be used anytime a thread calls a function in the audit plugin API.

      Attachments

        Issue Links

          Activity

            gopinathkarangula Gopinath added a comment - - edited

            Can this bug get attention, which is causing the system locks ? Will there be any bug fix for the latest community Audit Plugin ? As this bug encountered for 10.6.

            gopinathkarangula Gopinath added a comment - - edited Can this bug get attention, which is causing the system locks ? Will there be any bug fix for the latest community Audit Plugin ? As this bug encountered for 10.6.

            gopinathkarangula, this is not a bug, but a middle-priority feature request, which is currently not scheduled for any particular release.

            If you have any bug with system locks or anything, please, report it separately

            serg Sergei Golubchik added a comment - gopinathkarangula , this is not a bug, but a middle-priority feature request, which is currently not scheduled for any particular release. If you have any bug with system locks or anything, please, report it separately

            People

              Unassigned Unassigned
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.