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

Logically identical runtime configurations are not erased

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.4.13, 22.08.11, 23.02.8, 23.08.4
    • 24.02.0
    • Core
    • None
    • MXS-SPRINT-201

    Description

      If a runtime modification is done that is subsequently reverted and the configuration is logically identical to how it was on startup, the overriding file still remains. The desired behavior would be that only modifications that are meaningful should be persisted and configurations that are logically identical are discarded automatically.

      Attachments

        Issue Links

          includes

          Task - A task that needs to be done. MXS-4975 Discard global config if it returns to static state

          • Major - Major loss of function.
          • Closed
          is part of

          New Feature - A new feature of the product, which has yet to be developed. MXS-4761 Diff - Upgrade Risk Assessment Tool

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              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.