Sorry for the second post, I realized that my first post might not be clear...
I want the failover and the switch from "read-only" to "non read-only" to be dynamic, no downtime. Thanks -----Original Message----- From: [EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 4:07 PM To: Mysql General (E-mail) Subject: --read-only startup Hello all: I am trying to setup a multi-master environment that looks like a master-slave. Let me explain. My system will have all the clients talk to one server. If that server goes down, then it will fail to another. I want the setup to be multi-master so that upon fail-over, the other servers in the chain will get the changes. I have no problem setting up the multi-master environment. I want to take it a step farther. I would like to set up the "slaves" in this multi-master as read-only. Then, once they become the master, I want to drop the read-only attribute. I see, however, that in order to make a slave read-only, I have to start the server with the --read-only switch. I then assume that if I want to drop this attribute, I must stop the instance and then start it without the --read-only. I am wondering if anyone has more insight into this dilemma? Thanks - Gabe <><><><><><><><><><><><><><><><><><><><>><><> "Arise Arise A Rose A Rose" Gabriel Tucker 609 750 6668 - P 646 268 5681 - F <><><><><><><><><><><><><><><><><><><><>><><> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
