Re: streaming replication does not work across datacenter with 20ms latency? - Mailing list pgsql-general

From Tomas Vondra
Subject Re: streaming replication does not work across datacenter with 20ms latency?
Date
Msg-id 67a81ecff1e2fa67bbab94a310f2cd7b.squirrel@sq.gransy.com
Whole thread Raw
In response to Re: streaming replication does not work across datacenter with 20ms latency?  (Yan Chunlu <springrider@gmail.com>)
Responses Re: streaming replication does not work across datacenter with 20ms latency?  (Yan Chunlu <springrider@gmail.com>)
pgpool HA not working  (Sanjay Rao <srao@noida.interrasystems.com>)
List pgsql-general
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


pgsql-general by date:

Previous
From: Gavin Flower
Date:
Subject: Re: Implementing "thick"/"fat" databases
Next
From: Yan Chunlu
Date:
Subject: Re: streaming replication does not work across datacenter with 20ms latency?