Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fX70T-0000BL-4V for pgsql-admin@arkaria.postgresql.org; Sun, 24 Jun 2018 15:32:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fX70P-0000K0-Rc for pgsql-admin@arkaria.postgresql.org; Sun, 24 Jun 2018 15:32:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fX70P-0000Jt-KU for pgsql-admin@lists.postgresql.org; Sun, 24 Jun 2018 15:32:45 +0000 Received: from mtaout004-public.msg.strl.va.charter.net ([68.114.190.29]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fX70L-00080X-R2 for pgsql-admin@lists.postgresql.org; Sun, 24 Jun 2018 15:32:45 +0000 Received: from impout005 ([68.114.189.20]) by mtaout004.msg.strl.va.charter.net (InterMail vM.9.00.023.01 201-2473-194) with ESMTP id <20180624153239.UKFL3685.mtaout004.msg.strl.va.charter.net@impout005>; Sun, 24 Jun 2018 10:32:39 -0500 Received: from cerberus.crazybean.net ([24.151.10.150]) by impout005 with charter.net id 2fYe1y00P3EE3TL01fYeh1; Sun, 24 Jun 2018 10:32:39 -0500 X-Authority-Analysis: v=2.2 cv=Ts+WvHfh c=1 sm=1 tr=0 a=D2HTw/M6/8MmcHighGO7rg==:117 a=D2HTw/M6/8MmcHighGO7rg==:17 a=xqWC_Br6kY4A:10 a=7mUfYlMuFuIA:10 a=pGLkceISAAAA:8 a=vXe2j8XvKX7EPIDe7OMA:9 a=QEXdDO2ut3YA:10 a=gwC_pb7pSz-5elcRf44A:9 a=N2CdJA99UMOW6754:21 a=_W_S_7VecoQA:10 Received: from [IPv6:2001:470:e117:4:504:f50c:74e4:a390] (2001:470:e117:4:504:f50c:74e4:a390 [IPv6:2001:470:e117:4:504:f50c:74e4:a390]) by cerberus.crazybean.net (OpenSMTPD) with ESMTPSA id c6edf4e5 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 24 Jun 2018 11:32:38 -0400 (EDT) From: Rui DeSousa Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_BBC7CD6C-08F7-457B-AD56-D42CC5A80F41" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 Date: Sun, 24 Jun 2018 11:32:37 -0400 In-Reply-To: Cc: repmgr@googlegroups.com, pgsql-admin@lists.postgresql.org To: Mariel Cherkassky References: X-Mailer: Apple Mail (2.3445.8.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail=_BBC7CD6C-08F7-457B-AD56-D42CC5A80F41 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jun 24, 2018, at 4:59 AM, Mariel Cherkassky = wrote: >=20 >=20 > Now, How can I further investigate it ? my wal_keep_segment is = assigned to 100 but since friday 261 wals were generated so I guess I = dont have another option but to sync the node again. However, I want to = understand why it happened. What can you advice me to check ? >=20 What is the connectivity between the nodes, any firewalls? What=E2=80=99s= the settings for wal_sender_timeout and wal_receiver_timeout? Why not = use a replication slot or have it fail over to using the archived WALs = instead of full database restore? There should be other messages in Postgresql logs. --Apple-Mail=_BBC7CD6C-08F7-457B-AD56-D42CC5A80F41 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Jun 24, 2018, at 4:59 AM, Mariel Cherkassky <mariel.cherkassky@gmail.com> wrote:


Now, How can I further investigate it ? my wal_keep_segment = is assigned to 100 but since friday 261 wals were generated so I guess I = dont have another option but to sync the node again. However, I want to = understand why it happened. What can you advice me to check ?


What is the connectivity between the nodes, any = firewalls?  What=E2=80=99s the settings for wal_sender_timeout = and wal_receiver_timeout?  Why not use a replication slot or = have it fail over to using the archived WALs instead of full database = restore?

There should be other = messages in Postgresql logs.


= --Apple-Mail=_BBC7CD6C-08F7-457B-AD56-D42CC5A80F41--