我的互为备份的两台机子启动时怎么占用了大量的内存里cache空间

wangyih

原帖由 "大雪飞扬" 发表：
呵呵，看了大家的讨论，感觉：

1、数据库间同步在两边同时进行修改操作是会出现“脏”数据，这一点需要靠应用程序来解决。

2、配置成一个读，一个写，应该是一个不错的解决方案

兄弟一个读，一个写那还是互备吗？

aiwei

在理论上互备是可以的(小弟是根据Mysql 的HOWTO来理解），但实际上我做的互备只维持了２０几个小时就崩掉了．郁闷

jim.ma

...........看到后面怎觉得不太像讨论技术了。

第八天

真正意义上的双机互备是不支持的！这里是mysql官方文档的说法：
MySQL replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed (cross-server) update. In other words, it is possible for client A to make an update to co-master 1, and in the meantime, before it propagates to co-master 2, client B could make an update to co-master 2 that will make the update of client A work differently than it did on co-master 1. Thus, when the update of client A makes it to co-master 2, it will produce tables that are different than what you have on co-master 1, even after all the updates from co-master 2 have also propagated. This means that you should not co-chain two servers in a two-way replication relationship unless you are sure that your updates can safely happen in any order, or unless you take care of mis-ordered updates somehow in the client code

tiandexiao

我也不知道如何解决这样的问题噢。