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