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

MaxScale should detect conflicting configurations and refuse to start

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0
    • Core
    • None
    • MXS-SPRINT-62, MXS-SPRINT-63, MXS-SPRINT-64

    Description

      MaxScale should detect if two or more instances of MaxScale are running on the same computer and refuse to start if they are started in a way that causes conflicts between them.

      Case in point; MXS-1661 describes a situation where when there was an authentication error, MaxScale would log database is locked. The reason was that two MaxScale instances were running; both using the same cache directory and thus the same sqlite user database.

      When a second MaxScale instances is started, it should detect if there is such a conflict, log a descriptive error message, and refuse to start.

      Attachments

        Issue Links

          Activity

            People

              marko.rajala Marko Rajala (Inactive)
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.