Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-5952

MaxScale failover fails with MASTER_SSL=1 default in MariaDB 11.4

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 21.06.21, 22.08.18, 23.02.15, 24.02.7, 25.01.4
    • 24.02.8, 25.01.5
    • mariadbmon
    • None
    • MXS-SPRINT-244

    Description

      Starting from MariaDB 11.4, SSL is enabled on the server by default. This change also means that when a CHANGE MASTER command is executed, the option MASTER_SSL=1 is automatically applied by default.

      During a MaxScale switchover or failover, the CHANGE MASTER command is issued to redirect replication to the new master. However, even if replication_master_ssl=0 is configured in MaxScale and ssl is disabled at the server level, the generated CHANGE MASTER command still includes MASTER_SSL=1 as its default.

      MaxScale should honor replication_master_ssl=0 and override the default MASTER_SSL=1 setting introduced in MariaDB 11.4 when generating the CHANGE MASTER command.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            pandi.gurusamy Pandikrishnan Gurusamy
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.