-->-----Original Message----- -->From: Ian Neubert [mailto:[EMAIL PROTECTED] -->Sent: Thursday, August 07, 2003 1:00 PM -->To: Dathan Vance Pattishall -->Cc: [EMAIL PROTECTED] -->Subject: RE: MySQL Replication -->
-->Off hand do you know any good resources on how to setup a highly -->available -->and load balanced MySQL system? Setting up replication is easy enough, Highly available systems work generally in your design but here are some suggestions based on some things I've been doing. 1) Configure the 2 masters to share the same IP with VRRP. 2) The sub master or fail-over master needs to have the same data and same bin-log so CHANGE MASTER TO can be avoided on the slaves where a auto reconnect can reliably pick up from where they left off. - Suggestions mirror over the network or write the bin logs on a shared NFS device (another point of failure) 3) Software need to monitor the master / sub-master to fail over and keep the primary master down since fail back should be done manually. This is due to order of events such as repair etc -what happens 1st. There are a few steps I'm forgetting but this should work. -->but I -->can't find much data about getting the whole thing to work together so to -->speak (highly available writes). --> -->Thanks! --> -->....................... -->Ian Neubert -->Director of IS -->TWAcomm.com, Inc. -->http://www.twacomm.com/ --> -->-----Original Message----- -->From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED] -->Sent: Thursday, August 07, 2003 12:54 PM -->To: 'Ian Neubert'; [EMAIL PROTECTED] -->Subject: RE: MySQL Replication --> --> -->That configuration doesn't seem to work if I'm reading it right. A slave -->cannot have more then one master unless mysql more then 1 mysqld process -->running on different ports is used. --> -->-->For example, if a person places an order on our site, the update is -->sent -->-->to -->-->the master server. Can that update be replicated to the slaves before -->the -->-->browser is taken to a reciept page (which is queried against the -->slaves)? --> -->Also guaranteeing an event has occurred on a slave and building -->application logic dependent on this necessity is a tough problem to -->solve and you might as well query the master since you need to verify -->the event is there anyway as part of the conditional. --> -->The reason for my last statement, I've notice in 3.23.5x that -->replication lag can occur in many situations: -->- The master is loaded and is not able to stream the binary log file as -->fast. -->- Locks on the slave preventing updates to occur -->- Load on the slave is high -->- Invalid packet errors where the slave needs to reconnect -->- Some sort of error that stops replication --> --> -->With all of the above examples, I would not have application logic -->dependent on slave events. Instead code your applications based on the -->known limitations. --> -->For example a search engine. It does not necessarily need an up to date -->all of the time index of words and matches... --> --> -->-- -->Dathan --> --> --> -->-->-----Original Message----- -->-->From: Ian Neubert [mailto:[EMAIL PROTECTED] -->-->Sent: Thursday, August 07, 2003 11:27 AM -->-->To: [EMAIL PROTECTED] -->-->Subject: MySQL Replication -->--> -->-->Hello all, -->--> -->-->Can anyone share their experience with replication? In particular I'm -->-->wondering how fast (or how slow?) replication occurs. Could I pull -->off -->-->the -->-->configuration below? -->--> -->--> -->-->http://linux.ianneubert.com/images/mysql_failover.png or -->-->http://linux.ianneubert.com/images/mysql_failover.pdf -->--> -->-->Thanks for your insight! -->--> -->-->....................... -->-->Ian Neubert -->-->Director of IS -->-->TWAcomm.com, Inc. -->-->http://www.twacomm.com/ -->--> -->--> -->-->-- -->-->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] --> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
