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

Log Deprecation Warnings for Terminology Change

    XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      • So that users are aware of the terminology change and can update their configurations accordingly,
      • As a MaxScale user,
      • I want MaxScale to log deprecation warnings to the console and logs for the change from master/slave to primary/replica.

      Acceptance Test - Deprecation Warning in Console

      • Given MaxScale is configured using master/slave terminology
      • When MaxScale starts or reloads its configuration
      • Then a deprecation warning is displayed in the console
      • And the warning indicates the master/slave terminology will be replaced by primary/replica
      • And the warning provides guidance on updating the configuration

      Acceptance Test - Deprecation Warning in Logs

      • Given MaxScale is configured using master/slave terminology
      • When MaxScale starts or reloads its configuration
      • Then a deprecation warning is logged
      • And the log entry indicates the master/slave terminology will be replaced by primary/replica
      • And the log entry provides guidance on updating the configuration

      Acceptance Test - Deprecation Warning on Replication Commands

      • Given MaxScale is configured using master/slave terminology
      • When replication-related commands or operations are executed
      • Then a deprecation warning is displayed in the console and logs
      • And the warning indicates the master/slave terminology will be replaced by primary/replica
      • And the warning provides guidance on updating the configuration

      Acceptance Test - Warning Frequency

      • Given MaxScale is configured using master/slave terminology
      • When MaxScale starts or reloads its configuration multiple times
      • Then the deprecation warning is logged each time
      • And when replication-related commands are executed multiple times
      • Then the deprecation warning is logged at least once per session to avoid log flooding

      Acceptance Test - No Warning with Updated Terminology

      • Given MaxScale is configured using primary/replica terminology
      • When MaxScale starts or reloads its configuration
      • Then no deprecation warnings related to terminology are displayed in the console or logs
      • And MaxScale operates without any warnings about terminology changes

      Attachments

        Activity

          People

            maxmether Max Mether
            JoeCotellese Joe Cotellese (Inactive)
            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.