Mon Feb 2 14:54:15 PST 2009
- Previous message: [Slony1-general] setup where slave nodes can not connect each other
- Next message: [Slony1-general] Patch to have a defined table lock order
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 02.02.2009 um 23:50 schrieb Christopher Browne: > Tilman Baumann <tilman.baumann at collax.com> writes: >> My cluster has gone out of sync since I added another node. >> >> The setup has one master and two slaves. The master can connect both >> slaves but each of the slaves can only connect to the master not the >> other slave. >> Is this setup feasible? >> >> The Master has a store path for each of the slaves. But the slaves >> have only one to the master. >> But each node Listens every other. This was created by the slonik >> command subscribe set. >> Am I right in assuming that listen does not necessaryly implies >> dorect >> db connection aka. store path? > > If you run all of the slon processes on the "master" server, then > there won't be any issue; the slons will have access to all nodes. > That seems like the simplest resolution to this... Brilliant idea. This would also keep the passwords off the slaves.Great.
- Previous message: [Slony1-general] setup where slave nodes can not connect each other
- Next message: [Slony1-general] Patch to have a defined table lock order
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list