Hi Steve,<div><br></div><div>Firstly, Thanks for all the help to my other thread I raised and helping me in moving forward with my testing.</div><div>Am playing a bit with Slony these days on high end replication solutions. </div>
<div><br></div><div>Am using Slony-I 2.1.0, I followed the documentation for adding the node to the existing replication, however when I try to subscribe the new node its going into waiting. Am doing in localhost of same cluster with multiple databases.</div>
<div><br></div><div>1. Create database</div><div>create database slave2;</div><div><br></div><div>2. Restore the master structure to slave2;</div><div><br></div><div>pg_dump -h localhost -s -p 5432 -d master | psql slave</div>
<div><br></div><div>3. Drop _myrep schema which copied by pg_dump to slave ( Note: This is not documented, I suspect when we copy masterdb schema structure u also get the _slonyschema as well. Which throw error as _slonyschema existing. Do we really need master _slonyschema to new node ?)</div>
<div><br></div><div>psql -d slave -c "drop schema _myrep cascade;"</div><div><br></div><div>4. below is the script to add new node:</div><div><br></div><div>#!/bin/bash</div><div><div><br></div><div>slonik <<_eof_</div>
<div>cluster name = myrep;</div><div>node 1 admin conninfo='host=127.0.0.1 dbname=master user=postgres port=5432';</div><div>node 2 admin conninfo='host=127.0.0.1 dbname=slave1 user=postgres port=5432';</div>
<div>node 3 admin conninfo='host=127.0.0.1 dbname=slave2 user=postgres port=5432';</div><div><br></div><div>store node (id = 3, event node = 1, comment = 'Slave2 Node For The Primary postgres');</div><div>
<br></div><div>#Setting Store Paths ...</div><div>echo 'Stored all nodes in the slony catalogs';</div><div>store path(server = 1, client = 3, conninfo='host=127.0.0.1 dbname=master user=postgres port=5432');</div>
<div>store path(server = 3, client = 1, conninfo='host=127.0.0.1 dbname=slave2 user=postgres port=5432');</div><div>_eof_</div></div><div><br clear="all"><div>This goes fine..</div><div><br></div><div>5. When I do subscribe its going into waiting stage.</div>
<div><br></div><div>Subscribe script:</div><div><br></div><div><div>#!/bin/bash</div><div># Subscribe node</div><div><br></div><div>slonik <<_eof_</div><div>cluster name = myrep;</div><div>node 1 admin conninfo='host=127.0.0.1 dbname=master user=postgres port=5432';</div>
<div>node 2 admin conninfo='host=127.0.0.1 dbname=slave user=postgres port=5432';</div><div>node 3 admin conninfo='host=127.0.0.1 dbname=slave2 user=postgres port=5432';</div><div><br></div><div>try { subscribe set (id = 1, provider = 1 , receiver = 3, forward = yes, omit copy = false); } on error { exit 1; } echo 'Subscribed nodes to set 1';</div>
<div>_eof_</div></div><div><br></div><div>output of the subscribe node;</div><div><div>-bash-4.1$ ./new_node_subscribe-set.sh</div><div>waiting for events (3,5000000001) only at (3,0) to be confirmed on node 1</div><div>
waiting for events (3,5000000001) only at (3,0) to be confirmed on node 1</div><div>waiting for events (3,5000000001) only at (3,0) to be confirmed on node 1</div></div><div><br></div><div>I found the link which pointing to some bug. Correct me, how to achive this.</div>
<div><br></div><div><a href="http://www.slony.info/bugzilla/show_bug.cgi?id=223">http://www.slony.info/bugzilla/show_bug.cgi?id=223</a></div><div><br></div><div><br></div>-- <br>Regards<div>Raghav</div><div>Blog: htt://<a href="http://raghavt.blogspot.com/" target="_blank">raghavt.blogspot.com/</a></div>
<br>
</div>