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

Monitors add deprecated parameters to persisted config files

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.3.7
    • Fix Version/s: 2.3.9
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-84

      Description

      Folks,

      Adding the following basic config file:

      [maxscale]
      threads                     = auto
      log_augmentation            = 1
      ms_timestamp                = 1
      syslog                      = 1
      admin_host                  = 0.0.0.0
      admin_port                  = 8989
      admin_auth                  = 1
      admin_log_auth_failures     = 1
       
      [rwsplit-service]
      type                        = service
      router                      = readwritesplit
      user                        = maxusr
      password                    = C1ED520A2B298913FC15A16ECFC3E85D
      causal_reads                = true
      causal_reads_timeout        = 300
      transaction_replay          = true
      transaction_replay_max_size = 1Mi
      delayed_retry               = true
      delayed_retry_timeout       = 300
      master_reconnection         = true
      max_sescmd_history          = 500
      prune_sescmd_history        = true
      master_failure_mode         = fail_on_write
      max_slave_replication_lag   = 60
      

      Starting MaxScale, running the below to create monitor, servers and etc:

      maxctrl create monitor replication-monitor mariadbmon --monitor-user=maxmon --monitor-password=169BE1AF9B23E608BC46BC4C7053132E replication_user=mariadb replication_password=CCEA9580F578CF9FDA838242A1736813
       
      #: task: configuring the monitor for the replication cluster
      maxctrl alter monitor replication-monitor monitor_interval          100 
      maxctrl alter monitor replication-monitor failcount                 3 
      maxctrl alter monitor replication-monitor auto_failover             true 
      maxctrl alter monitor replication-monitor auto_rejoin               true
      maxctrl alter monitor replication-monitor enforce_read_only_slaves  true
      maxctrl alter monitor replication-monitor detect_replication_lag    true
      maxctrl alter monitor replication-monitor disk_space_threshold      /:85
      maxctrl alter monitor replication-monitor disk_space_check_interval 1000
       
      #: task: create a listener
      maxctrl create listener rwsplit-service rwsplit-listener 3306
       
      #: task: create servers
      maxctrl create server prod-mariadb01 1.1.1.1 3306
      maxctrl create server prod-mariadb02 2.2.2.2 3306
      maxctrl create server prod-mariadb03 3.3.3.3 3306
       
      #: task: link servers with the service
      maxctrl link service rwsplit-service prod-mariadb01
      maxctrl link service rwsplit-service prod-mariadb02
      maxctrl link service rwsplit-service prod-mariadb03
       
      #: task: link servers with the monitor
      maxctrl link monitor replication-monitor prod-mariadb01
      maxctrl link monitor replication-monitor prod-mariadb02
      maxctrl link monitor replication-monitor prod-mariadb03
      

      Everything was up and running and then I decided to give MaxScale a restart and then, I saw the below better:

      2019-06-09 23:07:05.389   warning: (param_is_deprecated): Parameter 'allow_cluster_recovery' for module 'replication-monitor' is deprecated and will be ignored.
      2019-06-09 23:07:05.389   warning: (param_is_deprecated): Parameter 'multimaster' for module 'replication-monitor' is deprecated and will be ignored.
      2019-06-09 23:07:05.389   warning: (param_is_deprecated): Parameter 'mysql51_replication' for module 'replication-monitor' is deprecated and will be ignored.
      

      The monitor file created at the default --persistdir=/var/lib/maxscale/maxscale.cnf.d yet is created with old vars:

      [replication-monitor]
      type=monitor
      servers=prod-mariadb01,prod-mariadb02,prod-mariadb03
      disk_space_threshold=/:85
      disk_space_check_interval=100
      detect_replication_lag=true
      enforce_read_only_slaves=true
      auto_rejoin=true
      auto_failover=true
      failcount=3
      monitor_interval=100
      password=169BE1AF9B23E608BC46BC4C7053132E
      user=maxmon
      replication_password=CCEA9580F578CF9FDA838242A1736813
      replication_user=mariadb
      backend_connect_timeout=3
      backend_read_timeout=1
      backend_write_timeout=2
      backend_connect_attempts=1
      journal_max_age=28800
      script_timeout=90
      events=all
      detect_stale_master=true
      detect_stale_slave=true
      mysql51_replication=false
      multimaster=false
      detect_standalone_master=true
      allow_cluster_recovery=true
      ignore_external_masters=false
      failover_timeout=90
      switchover_timeout=90
      replication_master_ssl=false
      verify_master_failure=true
      master_failure_timeout=10
      switchover_on_low_disk_space=false
      maintenance_on_low_disk_space=true
      handle_events=true
      assume_unique_hostnames=true
      module=mariadbmon
      

      Maybe it needs a review to remove deprecates.

      Thanks!!

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            wagnerbianchi Wagner Bianchi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration