From: | Dan Wierenga <dwierenga(at)gmail(dot)com> |
---|---|
To: | "Zhu, Joshua" <jzhu(at)vormetric(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: BDR, ERROR: previous init failed, manual cleanup is required |
Date: | 2018-02-07 21:45:08 |
Message-ID: | CA+g_LOkQYc1rMSJi2_KS5WR-nnWqKoxdnHWL7tQn0KA4uKc0UQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 7, 2018 at 9:14 AM, Zhu, Joshua <jzhu(at)vormetric(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | David Gauthier | 2018-02-07 21:47:58 | Re: "could not receive data from client" && "incomplete startup packet" |
Previous Message | Colin Morelli | 2018-02-07 21:22:56 | Re: Critical errors during logical decoding |