From: | Will McCormick <wmccormick(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | BDR - Remove & Join |
Date: | 2015-11-09 21:10:26 |
Message-ID: | CA+jgkY6A3j-wyPfVOxSVKyCKcbZCr_QtWs5RApCFmXUTOWuw8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a script which is meant to remove a node from bdr replication. Two
nodes in replication node A and node B. The script does the following.
1. On node A - SELECT bdr.bdr_part_by_node_names(ARRAY['node B']);
2. On node A -Checks that the node_status is marked as 'k' in bdr.bdr_nodes
3. I then drop the database on node B
4. On node A I remove all nodes from bdr.bdr_nodes which have a status 'k'
I then run a script which I used to setup replication before removal. The
problem I encounter is node B after join in bdr.bdr_nodes is stuck in
status 'c'.
Any advice here would be appricated. I'm not sure if I need to drop all
databases and reinstall postgres instead of step 3. Or f this should be
enough?
We are using the following version of bdr bdr | 16385 |
11 | f | 0.9.2.0 |
{18080,18095,18108,18143,18173,18183,18192,18199,18212,18281} |
{"","","","","","","","","",""} according to pg_extension.
Please let me know if there is further information I can provide to
troubleshoot or if this is a known issue.
Regards and thank you.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-11-09 21:30:52 | Re: run 2 instances of postgres 9.4 on same linux VM |
Previous Message | anj patnaik | 2015-11-09 19:40:02 | run 2 instances of postgres 9.4 on same linux VM |