On Wed, December 5, 2007 11:45 am, Sonia Hamilton wrote: > I'm working with MySQL5 replication at the moment. All is working fine > except for one problem - there's a large table on the Master that I > don't want to replicate (bandwidth), and the Master is running MySQL4. > > The MySQL manual refers to --replicate-ignore-table=db.tbl, but my > understanding of this is that the Slave retrieves all data made > available by the Master, *then* discards data based on ignore rules, > thus not solving my bandwidth issue. > > Can anyone confirm or deny this? > > Any suggestions for getting around the problem?
Hardly optimal but we did manage to get around it by running another MySQL server on the LAN and doing the ignore on that, then replicating from that to the remote site. We had a physical server laying around but these days something like OpenVZ or KVM (or other virtualisation systems) would do the trick. Actually... you don't have to do that either... I just remembered I did run another mysql server on a different port on the same machine. Perhaps one day some enterprising person might somehow manage to 'proxy' the replication more efficiently. -- ---<GRiP>--- Electronic Hobbyist, Former Arcadia BBS nut, Occasional nudist, Linux Guru, SLUG President, AUUG and Linux Australia member, Sydney Flashmobber, Tenpin Bowler, BMX rider, Walker, Raver & rave music lover, Big kid that refuses to grow up. I'd make a good family pet, take me home today! Some people actually read these things it seems. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
