[MXS-839] Implement read_only in mysqlmon to allow (a/semi-sync) multimaster setups with slaves Created: 2016-08-25  Updated: 2016-09-13  Resolved: 2016-09-13

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: None
Fix Version/s: 2.1.0

Type: New Feature Priority: Major
Reporter: Michaël de groot Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Hi,

I am working with a setup with 2 asynchronous masters. Each master has a slave. The inactive master has read_only enabled. It is an active/passive setup for the masters but active/active setup for the 2 slaves. The passive master shouldn't fall behind the master but we want to check replication lag on the slaves. This is not possible in the mmmon monitor.

I think the best solution would be to merge the functionality of mmmon into mysqlmon:
When I currently run the 4 servers in 1 mysqlmon, all 4 servers become slave. If there are 2 root nodes (or: a circular replication setup), initially both of the nodes should become master. Next, we check if any of them have read_only enabled. If they do, the master state should be removed from (or not added to) that node. This feature would make mmmon obsolete.

Thanks,
Michaël



 Comments   
Comment by markus makela [ 2016-09-13 ]

MySQL Monitor now supports the multimaster option which allows detection of multi-master topologies. The @@read_only variable is also read and understood.

Comment by Michaël de groot [ 2016-09-13 ]

Cool! Is the mmmon also deprecated?

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