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

MaxScale tries to start up if --export-config is used and a cached cluster configuration is present

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.2.4
    • 6.4.3, 22.08.1
    • Core
    • None

    Description

      If configuration synchronization is enabled and --export-config is used when a cached cluster configuration is present, MaxScale will attempt to start up normally instead of exiting once the configuration is verified and exported. If another MaxScale is already running, this will cause the export to fail.

      Another problem is that if the startup is fixed to not proceed past the verification phase, the configuration export will not produce any output as the static files it uses to produce the data will be empty.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.