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

wsrep_ready: OFF after MDL BF-BF conflict

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.6.7, 10.7.3
    • N/A
    • Galera
    • None
    • Ubuntu 20.04 LTS

    Description

      We are running a 2 node + arbitrator cluster.

      Galera sets WSREP_READY to OFF after MDL BF-BF conflict on second node.
      mariadb service does not crash

      logs:

      Apr 27 03:00:09 node02.mariadb mariadbd[1003]: 2022-04-27  3:00:09 8 [Note] WSREP: MDL BF-BF conflict
      Apr 27 03:00:09 node02.mariadb mariadbd[1003]: schema:  authc  
      Apr 27 03:00:09 node02.mariadb mariadbd[1003]: request: (8 #011seqno 3840795 #011wsrep (high priority, exec, executing) cmd 0 160 #011update `user` set `last_login` = '2022-04-27T01:00:09Z' where `id` = '131b4cd3-e390-4b31-b47d-d1a3d5cee3ee'<99><95>hb#023#001)
      Apr 27 03:00:09 node02.mariadb mariadbd[1003]: granted: (2 #011seqno 3840793 #011wsrep (toi, exec, committed) cmd 0 45 #011OPTIMIZE TABLE `log_history_daily`)
      Apr 27 03:00:09 node02.mariadb mariadbd[1003]: 2022-04-27  3:00:09 8 [ERROR] Aborting
      

      SHOW CREATE TABLE for the tables mentioned in the logs:

      CREATE TABLE `user` (
        `id` char(36) COLLATE utf8mb4_unicode_ci NOT NULL,
        `environment_id` char(36) COLLATE utf8mb4_unicode_ci NOT NULL,
        `username` varchar(64) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
        `password` char(60) COLLATE utf8mb4_unicode_ci NOT NULL,
        `status` enum('sign_up','invited','active','archived') COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'invited',
        `token` char(64) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
        `token_valid_till` datetime DEFAULT NULL,
        `last_login` datetime DEFAULT NULL,
        `password_updated_at` datetime DEFAULT NULL,
        `created_at` timestamp NULL DEFAULT NULL,
        `updated_at` timestamp NULL DEFAULT NULL,
        PRIMARY KEY (`id`),
        UNIQUE KEY `user_username_unique` (`username`),
        KEY `user_environment_id_index` (`environment_id`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
       
      CREATE TABLE `log_history_daily` (
        `type` enum('unknown','user','developer','api_key','api_env','mail_token','device') COLLATE utf8mb4_unicode_ci NOT NULL,
        `status` enum('valid','invalid') COLLATE utf8mb4_unicode_ci NOT NULL,
        `origin` enum('unknown','browser','go','android','ios','third_party') COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'unknown',
        `ip` varchar(45) COLLATE utf8mb4_unicode_ci NOT NULL,
        `value` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
        `user_id` char(36) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
        `date` date NOT NULL,
        `count` int(10) unsigned NOT NULL,
        `created_at` timestamp NULL DEFAULT NULL,
        `updated_at` timestamp NULL DEFAULT NULL,
        PRIMARY KEY (`type`,`status`,`origin`,`ip`,`value`,`date`),
        KEY `log_history_daily_user_id_foreign` (`user_id`),
        CONSTRAINT `log_history_daily_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `user` (`id`) ON DELETE SET NULL ON UPDATE CASCADE
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
      

      This happened on our test environment (mariadb 10.7.3) and our acceptance environment (mariadb 10.6.7)

      Attachments

        Issue Links

          Activity

            People

              janlindstrom Jan Lindström
              rtuk Rick Tuk
              Votes:
              6 Vote for this issue
              Watchers:
              8 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.