From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | milist ujang <ujang(dot)milist(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: BDR, wal segment has been removed, is it possible move forward? |
Date: | 2017-09-08 04:12:35 |
Message-ID: | CAMsr+YE1shAuYeCtvH7b895rAxqz8iPZ_uvH63msxt=3z+bxVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7 September 2017 at 21:16, milist ujang <ujang(dot)milist(at)gmail(dot)com> wrote:
> Hi Craig,
>
> On Wed, Sep 6, 2017 at 4:07 PM, Craig Ringer <craig(at)2ndquadrant(dot)com>
> 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?
>
Usually not. In this one specific case where a node is known to be fully
joined and online, but its status is stuck at 'i', yes.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | hamann.w | 2017-09-08 06:16:20 | Re: column names query |
Previous Message | Ron Johnson | 2017-09-08 03:48:52 | B-tree index on a VARCHAR(4000) column |