Re: streaming replication does not work across datacenter with 20ms latency?

From: Yan Chunlu <springrider(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: streaming replication does not work across datacenter with 20ms latency?
Date: 2011-07-24 12:46:26
Message-ID: CAOA66tEuTObhKFt-+LLX-aafUGuFPOu+i7oksG2687WGh0v1EQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

checkpoint_segments = 64
wal_keep_segments = 128

On Sun, Jul 24, 2011 at 8:25 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
> On 24 Červenec 2011, 6:09, Yan Chunlu wrote:
>> thanks for all the help!
>>
>> @Adrian:  yes, only one instance on each machine
>>
>> not the slave finally started and could be connect, replication didn't
>> begin, just following errors:
>> https://gist.github.com/1102225
>
> These errors just mean the master already removed WAL segments, so the
> slave can't actually start the replication because there'd be a gap. This
> usually happens with enough write activity (inserts, updates) when the
> slave is being setup.
>
> Whaht is your wal_keep_segments value? Increase it or set up WAL
> archiving, so that the slave can get the data.
>
> Tomas
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sanjay Rao 2011-07-24 13:25:09 pgpool HA not working
Previous Message Tomas Vondra 2011-07-24 12:25:26 Re: streaming replication does not work across datacenter with 20ms latency?