Hello! I've set up replication with a master and two slaves, all running 3.23.43, and it works like a charm. Except for...
When the master goes down, the slave tries to reconnect after 60 seconds, but just once. I expected it to retry until it can connect, because when the master comes up again, it should catch up on updates and everything would work like it should. I've got two radius servers that dig for user/pass hash information in the first available database, and the slave should always be as up to date as possible. When the master goes down for any reason, the slaves keep working and the setup seems to work very well (since there are hardly any updates, only password changes and occasional useradd). But when the master goes down for a period exceeding 60 seconds (well, the timeout interval), the slave thread exits and never tries to start replicating again, unless I manually do a SLAVE START on all the slaves. Is there a way to make a slave hammer the master indefinitely, until it can connect? I've read the manual several times, and found no clue... -- Jure Koren | unix administrator [EMAIL PROTECTED] | gnu/Linux software developer --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
