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

MariaDB crash if replication present between 2 different galera clusters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.5.13, 10.5.14
    • Fix Version/s: 10.5
    • Environment:

      Description

      Current infrastructure:
      1. Galera cluster (GC1) running MariaDB 10.3.32
      2. Galera cluster (GC2) running MariaDB 10.5.13 (tested also on 10.5.14)
      3. Asynchronous replication setup from GC1 -> GC2
      4. Both clusters have SSL configured
      5. Active traffic on GC1 (on node1 only)

      Working Scenario:
      1. GC2 running with 3-cluster members: up and running
      2. Replication configured between GC1 (node1) -> GC2 (node1): up and running

      Crash:
      1. On GC2 (node1), stop mariadb, and start -> Crash
      2. Repeats the same messages on each start attempt

      Workaround:

      • Add skip_replica_start in configuration file and start mariadb: OK
      • Then start replica threads (io_thread, sql_thread): Replication up and running
        > Note: Most of the time also fixes "Node dropped from cluster" error message.

      Crash Report: (attached as error.log_bug.txt)

      Can it be related to the mariadb_upgrade? (https://jira.mariadb.org/browse/MDEV-27789)

      Thanking you for checking.

        Attachments

          Activity

            People

            Assignee:
            jplindst Jan Lindström
            Reporter:
            Sarvesh Goburdhun Goburdhun Sarvesh Sharma
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.