Wed Dec 20 08:32:22 PST 2006
- Previous message: [Slony1-general] how to drop node when replication is lagging
- Next message: [Slony1-general] how to drop node when replication is lagging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Norman Yamada <nyamada at millburncorp.com> [061219 22:22]: > ?? Sorry -- what's the right node in that case? The master node? > In my case I have a master node and two slaves and one is definitely > lagging. So can I drop the slave node and as long as the master node sees > the event, I'm okay? Basically yes. All nodes that are still part of the cluster after the event, should see it. It should probably probagate from the master node without troubles. The only case where there might be troubles would be: MASTER <-> SLAVE1 <-> SLAVE2 If you drop SLAVE1, you've got a problem that SLAVE2 has no path to master. With 3 nodes that's usually not an issue, but I mention it because I was bitten at least once by stuff like that ;) Andreas
- Previous message: [Slony1-general] how to drop node when replication is lagging
- Next message: [Slony1-general] how to drop node when replication is lagging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list