[MXS-735] MySQL Monitor assigns both Master and Slave status to intermediate master Created: 2016-05-23  Updated: 2016-06-01  Resolved: 2016-06-01

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 1.4.3
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: markus makela Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

When multi-tiered replication topologies are used with the mysqlmon module, the intermediate masters get both the Master as well as the Slave status bits. This will cause problems when routers are looking for the true root master server and pick an intermediate master instead.



 Comments   
Comment by markus makela [ 2016-05-24 ]

The problem isn't really a problem as long as the replication topology depth is correctly detected.

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