Re: Slave claims requested WAL segment already removed - but it wasn't

From: Nick Cleaton <nick(at)cleaton(dot)net>
To: Jeff Beck <becked(at)fastmail(dot)fm>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Slave claims requested WAL segment already removed - but it wasn't
Date: 2016-06-03 07:36:16
Message-ID: CAFgz3ks-1RyW5YTeL9N8FT5m0dCB+Z4sxHq9wEqjTEXaAtk7hw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2 June 2016 at 02:43, Jeff Beck <becked(at)fastmail(dot)fm> wrote:
> Hi-
> We have a master (pg 9.4.4 on Ubuntu 14.10) and a slave (pg 9.4.8 on
> Centos 7). During a period of heavy use, the slave began complaining
> that the “requested WAL segment xxxxxx has already been removed”. But
> the WAL segment was still on the master. The issue was resolved by
> manually copying the pg_xlog directory over to the slave.
>
> I don’t see any errors on the master log file, or any other messages on
> the slave’s. What happened? How can this be prevented in the future?

I've seen this once. In my case there was a downstream slave of the
slave that I'd forgotten about, and the log entries on the slave were
the result of slave-of-slave asking slave for a WAL file that was not
present on slave.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Navis 2016-06-03 10:35:38 [pg_trgm] Making similarity(?, ?) < ? use an index
Previous Message Patrick Baker 2016-06-03 07:23:39 Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3