The thing is I'm looking for a solution with guaranteed transaction success. I have thought about building a layer that would guarantee transaction success. Say I had two duplicate databases and if a transaction failed on one it would still succeed on the other. Once the transaction failed it should take the failed database out of service. I believe this could be fairly straightforward but thought I would check the list to see if someone had already built a product or setup some system that would allow for this.
Dave Turner On Wed, May 29, 2002 at 05:21:39PM -0400, Moyer, Andy wrote: > I don't think this is specific for MySQL - I believe you can have it monitor > any processes you want it to. It also gets feedback from the system (core > temperature, power fluxuations, etc). We would have it monitor Apache, > MySQL, and any other core system components. The heartbeat cable is also > designed so that if one system dies (and stops sending the heartbeat), the > other system comes online. > > Also not sure about this, but I believe the systems share an IP address on > the network port, but the slave doesn't enable its network port until the > heartbeat dies or tells it to. If this isn't the case, they might include > something to update a NAT firewall configuration on the local network, but I > think it's actually the former. If it is the former, the slave is still > accessible through the heartbeat cable [probably]. > > You can get systems like this for under $10,000, but going with IBM and > super high redundancy, you're more likely to maintain the goal of > 100%(99.9%) uptime. > > - Andy --------------------------------------------------------------------- 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
