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

Rolling Upgrade from 10.6.22 to 10.11.15 failed with galera cluster

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Galera
    • None

    Description

      I try to rolling upgrade from 10.6.22 to 10.11.15 , but failed,
      Our environment is 3 nodes (node1+node2+witness),
      my operation steps as below:

      1#.stop node2
      systemctl stop mariadb-XXX_YYY

      2#.remove the old pkg and install new pkg

      yum remove galera-4-26.4.22 -y
      yum remove -y \
      MariaDB-compat-10.6.22 \
      MariaDB-backup-10.6.22 \
      MariaDB-client-10.6.22 \
      MariaDB-server-10.6.22 \
      MariaDB-common-10.6.22 \
      MariaDB-shared-10.6.22 \
      MariaDB-cracklib-password-check-10.6.22

      yum install galera-4-26.4.24-1.el8.x86_64.rpm -y
      yum install -y \
      MariaDB-common-10.11.15-1.el8.x86_64.rpm \
      MariaDB-server-10.11.15-1.el8.x86_64.rpm \
      MariaDB-backup-10.11.15-1.el8.x86_64.rpm \
      MariaDB-compat-10.11.15-1.el8.x86_64.rpm \
      MariaDB-shared-10.11.15-1.el8.x86_64.rpm \
      MariaDB-client-10.11.15-1.el8.x86_64.rpm \
      MariaDB-cracklib-password-check-10.11.15-1.el8.x86_64.rpm

      3#. start node2
      systemctl start mariadb-XXX_YYY

      *but node2 cannot startup, the mariadb.conf and db error log as attach file*

      Attachments

        1. mariadb.cnf
          7 kB
          johngou
        2. node1.txt
          28 kB
          johngou
        3. node2.txt
          42 kB
          johngou
        4. witness.txt
          10 kB
          johngou

        Activity

          People

            Unassigned Unassigned
            johngou johngou
            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.