[MXS-1894] MariaDBMon must show slave's GTID information when GTID is in use Created: 2018-06-02  Updated: 2019-05-28  Resolved: 2019-05-28

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.2.7
Fix Version/s: 2.3.0

Type: New Feature Priority: Major
Reporter: Wagner Bianchi (Inactive) Assignee: Todd Stoffel (Inactive)
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-1922 The GTID of Galera Nodes is not displ... Closed

 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).



 Comments   
Comment by markus makela [ 2019-05-28 ]

The maxctrl show monitors command appears to show the GTIDs so I'll close this as Done.

Generated at Thu Feb 08 04:10:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.