Removing and readding bdr nodes

From: Mathew Moon <mathew(dot)moon(at)vipaar(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Removing and readding bdr nodes
Date: 2015-05-01 04:40:23
Message-ID: CALXsgcQ83KFujCknG66B0=pprd1ysiJmEteCiDAP9oMxfpUf7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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
saying that it is already part of a bdr group. If I totally remove the
entire database from the node, deleting all of the data directory, and run
initdb on the data directory again and try to add the node to the group I
get errors saying that the other nodes expect this one to use its old sysid
and connect to its old replication slot. I don't understand how the other
nodes are identifying this one by its old information since I removed the
entire data directory and started over.

I saw in another thread that support for removing nodes is not complete but
surely there must be some way to do this even manually. How would one go
about removing ALL traces of an existing node from all of the others so it
was like it never existed before? Any help would be greatly appreciated.
BDR is the perfect solution for our infrastructure's needs for backup and
availability but we lack this one key ability to be able to roll it out for
production use.

Regards,
Mathew

Responses

Browse pgsql-general by date

  From Date Subject
Next Message recoverdata 2015-05-01 06:22:25 Re: Stellar Phoenix File Recovery Software
Previous Message Fabio Ugo Venchiarutti 2015-05-01 01:03:03 Re: PostgreSQL HA config recommendations