Mon Aug 4 15:05:21 PDT 2008
- Previous message: [Slony1-general] consulta slony a la inversa
- Next message: [Slony1-general] Drop Node fails after Failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi folks, Looking for some help here. I am using Slony-I 1.2.12 and have a simple 2 node Master/Slave environment. Node 1 is the Master/provider and node 2 is the slave/receiver. Node 1 goes down, ie database not accessible, and I failover to node 2: failover ( id = 1, backup node = 2); drop node ( id = 1); I receive the following error from the drop node command: Error: Node ID and event node cannot be identical Of note, when node 2 is the master/provider and node 1 is the slave/receiver, and I take node 2 database out of service, I am able to successfully failover to node 1 (using failover command and dropping the node). And subsequently reconfigure node 2 (store node, store path and subscribe set) to the replication set. I suspect the drop node is failing because when I configured Slony-I cluster, node 1 was established as the "origin" i.e.: init cluster (id = 1, comment = 'Node 1'); Yes I'm new to all of this, so any help/suggestions is appreciated!! Thank you! Carla McNearny -- View this message in context: http://www.nabble.com/Drop-Node-fails-after-Failover-tp18820805p18820805.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] consulta slony a la inversa
- Next message: [Slony1-general] Drop Node fails after Failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list