Re: BDR replication slots

From: Nikhil <nikhilsmenon(at)gmail(dot)com>
To: Alvaro Aguayo Garcia-Rada <aaguayo(at)opensysperu(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: BDR replication slots
Date: 2016-04-19 08:24:56
Message-ID: CALo-6YMCghXssZse0c+hhuthDEwYiDFoDhWTVdDhXv84iRW5cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On interface down:
------------------
<10.102.31.213(27599)postgres13082016-04-19 06:31:36
GMTprocess_journal%LOG: terminating walsender process due to replication
timeout

Once interface is brought back
----------------------------------------
425906 <12692016-04-19 08:32:58 GMT%LOG: starting background worker
process "bdr (6275149074578269365,2,16386,)->bdr (6275135922714263763,1,"
425907 <597732016-04-19 08:32:58 GMT%ERROR: relation "mygroup" already
exists
425908 <597732016-04-19 08:32:58 GMT%CONTEXT: during DDL replay of ddl
statement: CREATE TABLE public.mygroup (id pg_catalog."varchar"(14) NOT
NULL COLLATE pg_catalog."default", name pg_catalog."varchar"(100) COLLATE
pg_catalog."default", device_type pg_catalog."varchar"(30) COLLATE
pg_catalog."default", platform_type pg_catalog."varchar"(30) COLLATE
pg_catalog."default",
CONSTRAINT mygroup_pkey PRIMARY KEY (id) ) WITH (oids=OFF)
425909 <12692016-04-19 08:32:58 GMT%LOG: worker process: bdr
(6275149074578269365,2,16386,)->bdr (6275135922714263763,1,(PID 59773)
exited with exit code 1
425910 <10.102.31.213(13467)postgres597742016-04-19 08:32:59
GMTprocess_journal%LOG: starting logical decoding for slot
"bdr_16386_6275135922714263763_1_16386__"
425911 <10.102.31.213(13467)postgres597742016-04-19 08:32:59
GMTprocess_journal%DETAIL: streaming transactions committing after
0/1014CEE8, reading WAL from 0/1014A920
425912 <10.102.31.213(13467)postgres597742016-04-19 08:32:59
GMTprocess_journal%LOG: logical decoding found consistent point at
0/1014A920
425913 <10.102.31.213(13467)postgres597742016-04-19 08:32:59
GMTprocess_journal%DETAIL: There are no running transactions.
425914 *<10.102.31.213(13467)postgres597742016-04-19 08:32:59
GMTprocess_journal%LOG: unexpected EOF on standby con**nection*

On Tue, Apr 19, 2016 at 10:29 AM, Alvaro Aguayo Garcia-Rada <
aaguayo(at)opensysperu(dot)com> wrote:

> Hello,
>
> What do you see on each node's log after enablibg interfaces?
>
> Regards,
>
> Alvaro Aguayo
> Jefe de Operaciones
> Open Comb Systems E.I.R.L.
>
> Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC:
> (+51) 954183248
> Website: www.ocs.pe
>
> Sent from my Sony Xperia™ smartphone
>
>
> ---- Nikhil wrote ----
>
>
> Hello,
>
> I have a 2 node BDR group and replication is happening properly. if i
> bring down one of the node's interface, after sometime the replication
> slots are becoming inactive (pg_replication_slots view). Then if i bring
> back interface slots are not turning active automatically and replication
> stops. Any idea why automatically its not re-established ?
>
> Best Regards,
> Nikhil
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Иван Фролков 2016-04-19 12:37:43 How are files of tables/indexes/etc deleting?
Previous Message Jinhua Luo 2016-04-19 07:50:15 Re: Re: what's the exact command definition in read committed isolation level?