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

After upgrading from 10.6.16 to 10.6.19, a DB crashed frequently

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.19
    • None
    • None
    • None
    • RHEL8, VMWare, 2 active nodes plus a witness in a cluster running Galera 26.4.19.

    Description

      Hi MariaDB support team,

      Observation:

      • no stack trace/coredump is produced for checking further
      • no assertion error message appeared in mariadb-error.log
      • sudden crash, no signal 6, signal 11 or other signals in mariadb-error.log
      • sar CPU has spare capacity
      • sar memory was enough and no swapping
      • same version 10.6.19 executed for other similar systems (>300) but only 2 DBs w/ similar schema have this issue

      Next action:

      • suspect the problem is SQL / schema specific but could not pinpoint from binlog as failed SQLs are not captured in binlog
      • plan to enable audit (initially for DMLs) to track the offending SQL(s), may extend to DDL or even queries later
      • advise if there is better method to capture the offending SQL(s)

      Thanks and best regards,

      Lawrence

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              LawrenceMan Lawrence Man
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.