Hi, I've managed to answer my own question, deleting master.info in the data directory stops replication.
Thanks, Shane On 11/05/07, Shane Anderson <[EMAIL PROTECTED]> wrote:
Hi All, I currently have a MySQL solution configured in the following manner: <db01> -> <db-01-new> -> <db-reporting-01> db01 is currently our main database server and is replicating down to our new soon-to-be main database server db-01-new which is in turn replicating our reporting database db-reporting-01. db-01-new is currently acting as both a master and a slave, but once it becomes the new main database server and db01 is decomissioned it will only be a master. Basically I'm concerned that once db-01-new becomes the main database server that someone will accidentally start up the database server on db01 again and perform a write which will be replicated down to db-01-new. I can't work out how to permanently disable db-01-new from being a slave. Performing a 'stop slave;' isn't viable as the MySQL daemon will startup as a slave again if it is restarted. I've tried setting MASTER_HOST, MASTER_USER, etc to null but MySQL doesn't seem to like that. I've googled for an answer and looked through the MySQL site, but can't find anything. Any idea's? Thanks, Shane
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
