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 1fYCSb-0005t0-GM for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 15:34:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fYCSZ-0006FP-Rq for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 15:34:19 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYCSZ-0006FC-HU for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 15:34:19 +0000 Received: from mtaout001-public.msg.strl.va.charter.net ([68.114.190.26]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fYCSW-0000Mx-SL for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 15:34:18 +0000 Received: from impout002 ([68.114.189.17]) by mtaout001.msg.strl.va.charter.net (InterMail vM.9.00.023.01 201-2473-194) with ESMTP id <20180627153415.OOXZ3697.mtaout001.msg.strl.va.charter.net@impout002>; Wed, 27 Jun 2018 10:34:15 -0500 Received: from cerberus.crazybean.net ([24.151.10.150]) by impout002 with charter.net id 3raF1y0023EE3TL01raFHl; Wed, 27 Jun 2018 10:34:15 -0500 X-Authority-Analysis: v=2.2 cv=C6eZ8UH+ c=1 sm=1 tr=0 a=D2HTw/M6/8MmcHighGO7rg==:117 a=D2HTw/M6/8MmcHighGO7rg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=7mUfYlMuFuIA:10 a=pGLkceISAAAA:8 a=Xwi-4dro6KE5gKnEBiAA:9 a=3k-cCf8gbJW6KugJ:21 a=fs7pzt5rT3C9uRdJ:21 a=QEXdDO2ut3YA:10 Received: from [IPv6:2001:470:e117:4:654d:e9bd:3352:f405] (2001:470:e117:4:654d:e9bd:3352:f405 [IPv6:2001:470:e117:4:654d:e9bd:3352:f405]) by cerberus.crazybean.net (OpenSMTPD) with ESMTPSA id 87a288c5 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Wed, 27 Jun 2018 11:34:14 -0400 (EDT) Content-Type: text/plain; charset=utf-8 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 From: Rui DeSousa In-Reply-To: Date: Wed, 27 Jun 2018 11:34:14 -0400 Cc: Ron , pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <2E8EE382-0E75-4919-87CF-5EABCD26D3F3@crazybean.net> References: <70C74E85-F24B-4930-8942-5662540E0B74@crazybean.net> To: Mariel Cherkassky X-Mailer: Apple Mail (2.3445.8.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Jun 27, 2018, at 6:02 AM, Mariel Cherkassky = wrote: >=20 > Hi all, > it happened again. The weird thing is that when I query = pg_stat_replication I see only one slave(the one that is still synced) = and I dont see the second one. Moreover, I dont see anything in the = repmgr log of the primary and in the slave regarding the = disconnection... >=20 Right, once it drops out of replication it no longer shows up in = pg_stat_replication =E2=80=94 it is a live view of current active = connections. Does the replica report that the WAL has already been removed from = primary? If so most likely due to a spike in WAL file generation where = the setting wal_keep_segment is too low; However, I=E2=80=99m still = confused about your setup. Is the replica on the same subnet and what = is the network usages? Any large activity happening on the system, i.e. = index rebuilds? How many WALs where generated when the replica dropped = out?