Re: BDR replication slots

From: Sylvain Marechal <marechal(dot)sylvain2(at)gmail(dot)com>
To: Nikhil <nikhilsmenon(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: BDR replication slots
Date: 2016-04-19 07:01:09
Message-ID: CAJu=pHQm1UD8v_akBs6qid-0+fO57j7HmXg2A7dnuHPB4+aXmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2016-04-19 6:51 GMT+02:00 Nikhil <nikhilsmenon(at)gmail(dot)com>:

> 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 ?
>

May be postgres does not detect the link is down.
You could try modifying the connection strings, so that postgres detects
earlier the problem, like described in this post :
https://github.com/2ndQuadrant/bdr/issues/173 :

<<<
[...]
Example of dsn_connection field:
host=192.168.1.140 port=5432 dbname=safewalk-server connect_timeout=10
keepalives_idle=5 keepalives_interval=1
>>>

Hope this helps,

Sylvain

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jinhua Luo 2016-04-19 07:50:15 Re: Re: what's the exact command definition in read committed isolation level?
Previous Message Sachin Kotwal 2016-04-19 06:46:54 error while installing auto_explain contrib module