On 7 September 2017 at 21:16, milist ujang <ujang.milist@xxxxxxxxx> wrote:
Hi Craig,On Wed, Sep 6, 2017 at 4:07 PM, Craig Ringer <craig@xxxxxxxxxxxxxxx> wrote:You could drop and re-create the replication slot, I guess. But your nodes would be hopelessly out of sync and need manual resync (with data replication disabled) of one node vs another.Thanks for pointing to replication slot.I Simulate the similar situation in dev env by remove the wal segment on node1, when node2 keep inserting into a table, now it perfectly can move forward to latest wal segment, but the difference situation is at node_status.In production node_status is i in node1
there's a known bug in bdr1 where sometimes the node status doesn't update from 'i' after joining.
can I safely update the node_status directy on bdr.bdr_nodes?