Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lOkn9-0007xc-Fy for pgsql-admin@arkaria.postgresql.org; Tue, 23 Mar 2021 17:26:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lOkn8-0004F0-D4 for pgsql-admin@arkaria.postgresql.org; Tue, 23 Mar 2021 17:26:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lOkn7-0004Et-Pq for pgsql-admin@lists.postgresql.org; Tue, 23 Mar 2021 17:26:06 +0000 Received: from resqmta-po-04v.sys.comcast.net ([2001:558:fe16:19:96:114:154:163]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lOkn2-0007fT-DY for pgsql-admin@postgresql.org; Tue, 23 Mar 2021 17:26:05 +0000 Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233]) by resqmta-po-04v.sys.comcast.net with ESMTP id Og5ll3PaUbVMMOkmxlWjQN; Tue, 23 Mar 2021 17:25:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1616520355; bh=A8Xql1kseNYYlYeUze8DQfJWMlhg9HlxcKJojbfiFf8=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=Ebfu7jVWiQwiUKjaKPiWt69PERONgG2GTlmNfgnsyJBkvpQmK5bPq1a6/x3YWkLvU 5oh5HbIHVGisFd7j6fjvUYdwViN2MdnZ/FsskmyVBtvHptkdzQzmertXuJ6JhgfmKA zNhHwjbED4aFjN0Gfb3MGw1ti9dmQnVy1f1+kWzczXVQwD6NbMqhF7AJgJyStYjhJK CtegYRHnSerY8PTDLszoNP8PMLuOESsTFexxbFj4yP4Ac+BIA1byE0UKRpOpl16qzf 5P8WZSOSlysKnUS122C29AT4x2pi9hiT1t9S++3jPnsXfx5FUSShh6kGwxPgzyvkvi KHLiny8eEavlw== Received: from jsievers.comcast.net ([12.187.116.132]) by resomta-po-09v.sys.comcast.net with ESMTPA id OkmdlBVVmDxZcOkmelIyL6; Tue, 23 Mar 2021 17:25:41 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduledrudegiedguddttdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecunecujfgurhephffvufffkfgfgggtsehttdertddtredtnecuhfhrohhmpeflvghrrhihucfuihgvvhgvrhhsuceoghhsihgvvhgvrhhsudelsegtohhmtggrshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeevgfetjedvvdetkeejffduveffudetfeduheekheehkeehuedvhfekheefgfdvieenucffohhmrghinhepfhhoohgtohhrphdrtghomhenucfkphepuddvrddukeejrdduudeirddufedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohepjhhsihgvvhgvrhhsrdgtohhmtggrshhtrdhnvghtpdhinhgvthepuddvrddukeejrdduudeirddufedvpdhmrghilhhfrhhomhepghhsihgvvhgvrhhsudelsegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepphhgshhqlhdqrggumhhinhesphhoshhtghhrvghsqhhlrdhorhhg X-Xfinity-VMeta: sc=0.00;st=legit Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 4453A26005A for ; Tue, 23 Mar 2021 12:25:35 -0500 (CDT) From: Jerry Sievers To: pgsql-admin@postgresql.org Subject: Odd OS, SAN or related throughput issue affecting large streamer Date: Tue, 23 Mar 2021 12:25:35 -0500 Message-ID: <87o8f9n5o0.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Greetings! I do not know if $issue has anything to do w/Pg directly but would be very grateful for any insights... We've got ~20 servers on a beefy physical host that's using a fibre-channel storage array backend. Runtime and OS software was updated recently, and about 2 days ago, our big monster system began lagging in replication. It generally is able to stream WALs from the primary, but is no longer able to apply them and the slowdown is orders of magnitute below what it was prior. Full reboot of the host restores adequate throughput for several hours, upon which time the backlogging resumes. We have whitnessed the reboot as temp fix and then repeated falloff twice now on consecutive days. System of interest is a churny, ~50TB warehouse w/4 tablespaces. I' unclear on whether all or just some of them are sluggish on writes. It is "replay" lag, not lag in streaming that is evident. my SysEng team is so far unable to spot what's causing the issue. Suggestions re where to look next? Thx! postgres=# select version(); version ----------------------------------------------------------------------------------------------------------------------------------------------- PostgreSQL 11.11 (Ubuntu 11.11-1.pgdg16.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609, 64-bit $ uname -a Linux foobox.foocorp.com 4.15.0-139-generic #143~16.04.1-Ubuntu SMP Wed Mar 17 08:10:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- Jerry Sievers Postgres DBA/Development Consulting