Thanks a lot for your reply… I’ve already gone with the extreme route of dropping/recreating the database before trying the bdr_connections_changed() call, which I’ll keep in mind next time when the same issue happens.
From: Dan Wierenga [mailto:dwiere...@gmail.com] Sent: Wednesday, February 07, 2018 1:45 PM To: Zhu, Joshua <j...@thalesesec.net> Cc: pgsql-gene...@postgresql.org Subject: Re: BDR, ERROR: previous init failed, manual cleanup is required On Wed, Feb 7, 2018 at 9:14 AM, Zhu, Joshua <j...@vormetric.com<mailto:j...@vormetric.com>> wrote: Here is a BDR problem we ran into recently: A BDR group with a pair of nodes, N1 and N2, group is created on N1, N2 joins the group, so far so good N2 departs/rejoins the group a couple of times, then ran into an issue, with the following symptom, after executing bdr.bdr_group_join() on N2 wrt N1: FWIW, I was never able to successfully join a node with bdr.bdr_group_join. I was only ever able to get it to work by using bdr_init_copy and letting it create the database on the target node for me. Run "SELECT bdr.bdr_node_join_wait_for_ready();" to make sure it bootstrapped properly. I can't access my bdr cluster right now, but off the top of my head: - check the bdr.bdr_connections table in addition to the nodes table. - make sure you run "select bdr.bdr_connections_changed();" after you manually delete from any of the bdr tables.
