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

maxctrl does not persists dynamic changes for writeq_high_water and writeq_low_water

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.4.8
    • Fix Version/s: N/A
    • Component/s: maxctrl
    • Labels:
    • Environment:
      CentOS Linux release 7.6.1810 (Core)

      Description

      I'm updating the global maxscale configurations writeq_high_water and writeq_low_water with maxctrl dynamic commands, expecting to have new values configured for those both variables persisted at the --persistdir. I already have a global-options.cnf file there.

      [BIANCHI LABS] root@opmxs01: ~ # systemctl restart maxscale.service
      [BIANCHI LABS] root@opmxs01: ~ # maxscale --version
      MaxScale 2.4.8
      [BIANCHI LABS] root@opmxs01: ~ # maxctrl show maxscale | grep "writeq"
      │              │     "writeq_high_water": 0,                                  │
      │              │     "writeq_low_water": 0,                                   │
      And then, I issued below commands:
      [BIANCHI LABS] root@opmxs01: ~ # maxctrl alter maxscale writeq_high_water 32Mi
      OK
      [BIANCHI LABS] root@opmxs01: ~ # maxctrl alter maxscale writeq_low_water 512Ki
      OK
      
      

      Ok, checking maxscale global configurations:

      [BIANCHI LABS] root@opmxs01: ~ # maxctrl show maxscale | grep "writeq"
      │              │     "writeq_high_water": 33554432,                           │
      │              │     "writeq_low_water": 524288,                              │
      
      

      Checking the --persistdir :

      [BIANCHI LABS] root@opmxs01: ~ # ls -lh /var/lib/maxscale/maxscale.cnf.d/*
      -rw-r--r--. 1 maxscale maxscale 101 May 19 18:28 /var/lib/maxscale/maxscale.cnf.d/global-options.cnf
      [BIANCHI LABS] root@opmxs01: ~ # cat /var/lib/maxscale/maxscale.cnf.d/global-options.cnf
      [maxscale]
      auth_connect_timeout=3
      auth_read_timeout=1
      auth_write_timeout=2
      admin_auth=true
      passive=0
      
      

      Is it expected to not persist those configurations? More interesting yet is that if I change the passive mode from false to true , it persists it:

      [BIANCHI LABS] root@opmxs01: ~ # maxctrl alter maxscale passive true
      OK
      [BIANCHI LABS] root@opmxs01: ~ # cat /var/lib/maxscale/maxscale.cnf.d/global-options.cnf
      [maxscale]
      auth_connect_timeout=3
      auth_read_timeout=1
      auth_write_timeout=2
      admin_auth=true
      passive=1
      

      It is, maybe, something to take a look?

      [BIANCHI LABS] root@opmxs01: ~ # ls -lh /var/lib/maxscale/maxscale.cnf.d/
      total 4.0K
      -rw-r--r--. 1 maxscale maxscale 101 May 19 18:37 global-options.cnf
      [BIANCHI LABS] root@opmxs01: ~ # cat /var/lib/maxscale/maxscale.cnf.d/global-options.cnf
      [maxscale]
      auth_connect_timeout=3
      auth_read_timeout=1
      auth_write_timeout=2
      admin_auth=true
      passive=1
      [BIANCHI LABS] root@opmxs01: ~ # maxctrl show maxscale | grep "writeq"
      │              │     "writeq_high_water": 32000000,                           │
      │              │     "writeq_low_water": 512000,                              │
      [BIANCHI LABS] root@opmxs01: ~ # systemctl restart maxscale.service
      [BIANCHI LABS] root@opmxs01: ~ # maxctrl show maxscale | grep "writeq"
      │              │     "writeq_high_water": 0,                                  │
      │              │     "writeq_low_water": 0,                                   │
      
      

      Thanks, folks!

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              wagnerbianchi Wagner Bianchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.