[MXS-3162] Move EVENTS' status to Master in traditional/asynchronous replication Created: 2020-09-07  Updated: 2021-08-04  Resolved: 2020-10-23

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

Type: Bug Priority: Major
Reporter: Claudio Nanni Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: need_feedback

Attachments: File maxscale_event_test.log    
Issue Links:
Relates
relates to MXS-1937 Failover/switchover does not disable/... Closed

 Description   

When the Master is failed or switched over to a Slave events that will happen on the previous Master will not propagate to the other nodes.
MaxScale should enable the EVENT on the Master after switch|failover, row based replication.

 Comments   
Comment by Claudio Nanni [ 2020-09-07 ]

These scripts can help in the meantime:

https://mariadb.com/kb/en/mariadb-maxscale-23-mariadb-monitor/#promotion_sql_file-and-demotion_sql_file

Comment by markus makela [ 2020-10-23 ]

Testing with latest versions seems to show that this is no longer relevant.

Comment by Claudio Nanni [ 2020-10-23 ]

I confirm that:
2.3.20
2.4.13
2.5.4
Do not present the problem.
EVENTs are properly moved to the Master, consequently the replication subsystem sets EVENTs on Slaves to SLAVESIDE_DISABLED.

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