On Mon, Mar 22, 2010 at 7:52 PM, Jeremy Zawodny <jer...@zawodny.com> wrote: > Robert... > > On Mon, Mar 22, 2010 at 12:43 PM, Robert Hodges > <robert.hod...@continuent.com> wrote: >> >> Hi All, >> >> 1.) What are the "big" problems in replication? Let's say we have things >> like availability and basic read scaling basically handled. What's next >> on >> the list? (Big data, No-SQL, replication/database impedance mismatch due >> to >> faster hardware, complex topologies, management, etc., all suggestions are >> welcome.) > > Latency. Specifically I want muli-threaded replication so I can better take > advantage of mutli-core slaves. I'm willing to assume the "risk" associated > with saying "yes, I'm sure that each of these logical dbs are logically > separate, and no statements will cross them."
Paul started it, so I will add another plug. Are your slaves IO bound? If so, have you tried mk-slave-prefetch? I think it can fix the replication lag problems for IO bound slaves. It needs more people to test and use it. It can be used right now. I don't know if it good enough yet. We have sponsored a lot of work on it because we think it can be good enough. It won't do anything for workloads with crazy and gigantic joins or deletes/updates with full-table scans on large tables. Those problems require education, not faster replication. -- Mark Callaghan mdcal...@gmail.com _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
