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

MariaDBMon must show slave's GTID information when GTID is in use

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.2.7
    • Fix Version/s: 2.3.0
    • Component/s: mariadbmon
    • Labels:
      None

      Description

      Folks,

      I have created a pool of slaves for receiving reads on a dedicated Maxscale port. The monitor is MariaDBMon and the router is the Readconnroute. I would like to see information about the current GTID on my slaves when they are configured to replicate with that protocol:

      Monitor:                0x22d9260
      Name:                   Read-Pool-Monitor
      State:                  Running
      Sampling interval:      2000 milliseconds
      Connect Timeout:        3 seconds
      Read Timeout:           1 seconds
      Write Timeout:          2 seconds
      Connect attempts:       1
      Monitored servers:      [165.227.225.138]:3306, [138.68.158.166]:3306, [165.227.225.121]:3306
      Automatic failover:     Disabled
      Failcount:              5
      Failover timeout:       90
      Switchover timeout:     90
      Automatic rejoin:       Disabled
      Enforce read-only:      Disabled
      MaxScale monitor ID:    0
      Detect replication lag: Enabled
      Detect stale master:    Enabled
       
      Server information:
      -------------------
       
      Server:                 async01
      Server ID:              100
      Read only:              NO
      Slave configured:       YES
      Slave IO running:       YES
      Slave SQL running:      YES
      Master ID:              3
      Master binlog file:     mariadb-bin.000047
      Master binlog position: 392035153
       
      Server:                 async02
      Server ID:              200
      Read only:              NO
      Slave configured:       YES
      Slave IO running:       YES
      Slave SQL running:      YES
      Master ID:              4
      Master binlog file:     mariadb-bin.000051
      Master binlog position: 392033830
       
      Server:                 async03
      Server ID:              300
      Read only:              NO
      Slave configured:       YES
      Slave IO running:       YES
      Slave SQL running:      YES
      Master ID:              5
      Master binlog file:     mariadb-bin.000050
      Master binlog position: 392035121
      

      Is it possible to have that? It's going to be of great visibility, mainly when you need to make sure a set of slaves has the same GTID all around due to failover requirements (mainly when using @@gtid_strict_mode).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              toddstoffel Todd Stoffel
              Reporter:
              wagnerbianchi Wagner Bianchi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: