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

Index corruption after 10.4 upgrade

    XMLWordPrintable

    Details

      Description

      Hi,

      done an upgrade of MariaDB Server from 10.3.21 to 10.4.12, and encountered the following errors after replication process restarted:

      2020-02-10 16:00:27 4 [ERROR] InnoDB: Unable to find a record to delete-mark
      InnoDB: tuple DATA TUPLE: 3 fields;
      0: len 32; hex 6464343936316561363264373763666362663630663635396563323231343463; asc dd4961ea62d77cfcbf60f659ec22144c;;
      1: len 4; hex 00b2d13e; asc >;;
      2: len 4; hex 00662119; asc f! ;;

      InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
      0: len 30; hex 646434393565626136316631333938666539313237383038626463633031; asc dd495eba61f1398fe9127808bdcc01; (total 32 bytes);
      1: len 4; hex 00e4975d; asc ];;
      2: len 4; hex 00564157; asc VAW;;
      2020-02-10 16:00:27 4 [ERROR] InnoDB: page [page id: space=2383, page number=2684675] (304 records, index id 4183).
      2020-02-10 16:00:27 4 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

      Actually, a workaround is to optimize all tables on all schemas between (10.3 restore and 10.4 upgrade process) and (replication restart, or any other first transaction after restart of the instance)

      First time having this strange behaviour after doing lots of server migrations, case reproduced on others servers with the same OS and DB setup

      Thanks
      Emmanuel

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              E O
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.