Message-ID: <53AC4EEC.2000803@gmail.com>
Date: Thu, 26 Jun 2014 12:48:44 -0400
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Wal archive way behind in streaming replication
References: <53A9B567.5070301@gmail.com> <53A9C139.2040704@gmail.com>
 <3709F6AF-032E-4095-B0CB-DC1CE36F6B4B@breakthroughfuel.com>
In-Reply-To: <3709F6AF-032E-4095-B0CB-DC1CE36F6B4B@breakthroughfuel.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

OK, starting over...

I killed off both standby servers and I rebuilt my databases off of the primary server (10.10.1.128) using:

pg_basebackup -h 10.10.1.128 -p 5432 -D /var/lib/pgsql/9.3/data -X s -c fast

It took about 40 minutes to complete for each standby. Immediately after it completed, I copied my previously saved recovery.conf file into each's data directory and started the 
standby servers. I did not do anything to the files in the directory specified by the restore_command. Now, I would expect the primary to continue writing WAL segments into the 
directory while the pg_basebackup is running, but it apparently did not. Checking the primary's pg_xlog directory showed that it was now writing *DF, and each standby had only 
received up to *D5. That means each standby's WALs are about 1 hour behind. I would expect each to be at *DE as that should be the last completely written WAL file, and I would 
guess that the primary is still writing *DF.

The archive process on the primary is now writing WAL segments to the directory in archive_command, as I just saw *D6 pop into it, but it's never going to catch up without help as 
it's only copying 1 file every 10 minutes as a new one gets generated. Am I missing a flag for pg_basebackup? Or should I just accept that the standby's could never catch up with 
WAL segments and just turn archiving off?
--
Jay


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin