Configuration Synchronization and maintenance

18 views
Skip to first unread message

Sergio Bernal Ponce

unread,
Jan 25, 2024, 6:05:58 AM1/25/24
to MaxScale
Hello,

I would like to ask if it is expected to have a server going into maintenance mode in "Slave, Running" state and when clearing that, returns as just "Running" because the GTID of the Master has increased maybe as a result of the config_sync activity?.
Is there a way to quickly re-sync with the master beside manually re-configuring the replica based on the current Master GTID?
Is there an explanation on why this is not being done automatically that you could share?

Thanks in advance for your answers! :)


Markus Mäkelä

unread,
Jan 25, 2024, 6:11:58 AM1/25/24
to maxs...@googlegroups.com

Hi,

Replication lag alone should not cause the Slave label to be dropped. Does the Slave label get added back to the server after a while? If not, did the SQL thread of the replicating server stop with an error?

Markus

--
You received this message because you are subscribed to the Google Groups "MaxScale" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maxscale+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/maxscale/c9997c2c-74b1-4c75-b006-8a3597f4e716n%40googlegroups.com.
-- 
Markus Mäkelä, Senior Software Engineer
MariaDB Corporation

Sergio Bernal Ponce

unread,
Jan 25, 2024, 7:57:38 AM1/25/24
to MaxScale
Thanks Markus,

Restarted both servers and everything works like a charm, now I can put servers into maintenance and clear them without losing the Slave label. I don't know what was it, logs just showed that the monitor user didn't have enough grants, but I didn't change anything, just restarted services and it works.

I appreciate your clarification, it helped me to understand how it should be.

Reply all
Reply to author
Forward
0 new messages