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

Index Corruption in mariadb 10.5.11 slave

    XMLWordPrintable

    Details

      Description

      We have a simple mariadb replication with a master and a bunch of slaves. without any prior alert or warning, randomly in our slaves some indexes ( some of them are not present in master) become corrupted. This happened for us after migrating from we receive a bunch of error log each time.
      it happened for us several times we upgraded one of our slaves to mariadb 10.6 but it happened again.
      mariadb hung when it want to insert (or update ) a row because it cannot renew its index Btree I think. and the major error is because of SEMAPHOR timeout.
      I have attached our error logs.
      some times it says you hit a bug, some times it says the index is corupted.
      we have enough resources ( more than 180 G of ram and SSD Disk and 56 core CPU )
      the command that we used for creating the indexes is :
      alter table foo add index bar_idx(bar), algorithm =inplace, lock=none;

        Attachments

        1. mariadb.err
          29 kB
        2. mariadb.err.1
          182 kB
        3. mariadb.err.2
          99 kB
        4. mariadb.err-1.2
          99 kB
        5. mariadb-1.err
          151 kB
        6. mysqld.cnf
          3 kB
        7. slave.cnf
          0.7 kB

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              mamoghandi Mamo
              Votes:
              1 Vote for this issue
              Watchers:
              7 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.