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

From: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
To: "Yan Chunlu" <springrider(at)gmail(dot)com>
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:25:26
Message-ID: 67a81ecff1e2fa67bbab94a310f2cd7b.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Yan Chunlu 2011-07-24 12:46:26 Re: streaming replication does not work across datacenter with 20ms latency?
Previous Message Sim Zacks 2011-07-24 09:53:49 Re: Update columns in same table from update trigger?