Sorry for the paleo post but curious if there was ever a resolution for
this issue regarding BDR member join/eject:
https://goo.gl/N7FoUB
I'm currently seeing very similar behavior for the latest version of BDR
where cluster nodes are very confused about the state of their
connections/replication
On 17 May 2015 at 04:14, Mathew Moon wrote:
> Hi,
>
> Wanted to "bump" this (Is that ok in this list?). Like I mentioned, I see
> now that the error I am seeing in the log possibly indicates that the node I
> am "reinitializing" is creating a slot that points to its own old sysid.
> Checking manua
Hi,
Wanted to "bump" this (Is that ok in this list?). Like I mentioned, I see now
that the error I am seeing in the log possibly indicates that the node I am
"reinitializing" is creating a slot that points to its own old sysid. Checking
manually I see that this slot does in fact exist. I still
I just realized this also. The node that was removed and recreated shows
only one replication slot once it is recreated. That slot has its own id in
it too. That appears to be the problem. I have no idea why when creating it
the first time the slots for the other two nodes are created correctly, bu
Hi Craig,
Thank you for your reply. Below you will see the entire process that I have
used along with relevant log output. Something else that I have noticed is
that the status of nodes in bdr.bdr_nodes stays 'i' on the first server
that I initialize (lets call it primary and the others backups fo
On 1 May 2015 at 12:40, Mathew Moon wrote:
> Hi,
>
> I have a group of 5 bdr nodes and before we can move to production with
> them we must demonstrate that we can remove a node from the group and add
> that node back later. When I remove a node it stays in the bdr.bdr_nodes
> view with status 'k
Hi,
I have a group of 5 bdr nodes and before we can move to production with
them we must demonstrate that we can remove a node from the group and add
that node back later. When I remove a node it stays in the bdr.bdr_nodes
view with status 'k'. If I try to add that node back the node itself errors
