On 02/05/13 10:03, Marlen Caemmerer wrote:
Hey,
On Wed, 1 May 2013, Ryan Lane wrote:
On Wed, May 1, 2013 at 5:03 PM, Tim Landscheidt tim@tim-landscheidt.dewrote:
There were never answers to this, so I bring it up here again:
- How were "almost /all/ of the problems the TS have had with replication" "caused by that redundancy and trying to keep it synced"?
Thanks for this question :) - I also want to know. From my perspective it does not look like this and even the data inconsistencies appear when we have no commons copy on a mysql instance. And: DaB experimented with federated tables for commons too and we decided to not do this since it does not perform from the start. Probably nowadays when I planned something new in this area (which does not seem to make sense for TS) I'd really give Galera a try - http://codership.com/content/using-galera-cluster
FWIW, my {{ref needed}} phrase in the log was also intended to that statement by Coren, not to multichill reply.
Additionally, I rembember you data inconsistencies happen even with native mysql replication (as informed by Nosy earlier).