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

[Limitation?] Replay server doesn't start with storage engine enabled

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • None
    • N/A
    • None
    • None
    • Q2/2026 Server Development, Q3/2026 Server Development

    Description

      Issue:
      --------
      mtr test runs with federated storage engine enabled
      Replay server doesn't enable it , hence create table fails

      ReplayTest: Query failed on replay server: 1286 Unknown storage engine 'FEDERATED'
      ReplayTest: Failed query was: CREATE TABLE `fed_t1` (
      `foo_id` bigint(20) unsigned NOT NULL,
      `foo_name` varchar(255) DEFAULT NULL,
      `parent_foo_id` bigint(20) unsigned DEFAULT NULL,
      PRIMARY KEY (`foo_id`),
      KEY `foo_name` (`foo_name`),
      KEY `parent_foo_id` (`parent_foo_id`)
      ) ENGINE=FEDERATED DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci CONNECTION='mysql://root@127.0.0.1:19030/test/t1'

      How to repro:

      ./mtr federated.optimizer --replay-server
      

      Attachments

        1. mtr.txt
          163 kB
          Pavithra Pandith

        Issue Links

          Activity

            People

              bsrikanth Srikanth Bondalapati
              mariadb-pavithrapandith Pavithra Pandith
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 0.5d
                  0.5d
                  Remaining:
                  Remaining Estimate - 0.5d
                  0.5d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                  Git Integration

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