To be clear: Replication in MySQL replicates the DML (data manipulation language) and DDL (data definition language) commands -- that is, any command that's an alter, update, insert, replace, create, drop, etc statement to the slave.
If you write to the slave, it does not write back to the master. If you change the data on the slave server, replication from the master to the slave will happily continue (hopefully, unless you've changed something that would cause a duplicate key error or something) because it only sends the commands over. There's no way for the master to tell that the slave has changed. There is also no easy way to take a master and a slave and ensure that they do, indeed, have the same data. -Sheeri On 1/6/06, Jason Williard <[EMAIL PROTECTED]> wrote: > I am trying to understand exactly how replication works. So far, I see that > changes made on a master server are replicated to the slave server(s). > However, if a change is made on a slave server, is that replicated back to > the master as well as all other slaves? > > > I am asking this question as I try to develop a plan for more efficient web > servers. Here is what I am planning. Please let me know if this sounds > smart, or like a bad idea. > > Server 1: Redhat MySQL Master > Servers 2 & 3: Load-Balanced Redhat Apache web servers w/MySQL Slaves > > Servers 2 & 3 will be serving the same content and will need access to the > same data from the MySQL server(s). I am hoping that running MySQL on each > of the web servers will help to reduce the overall load on the servers. > > > ---- > Thank You, > Jason Williard > > > > > -- > 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]
