From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A0CD17BD5D for ; Wed, 13 Jul 2022 12:41:50 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8F84E1726 for ; Wed, 13 Jul 2022 12:41:20 +0200 (CEST) Received: from kerio.tuxis.nl (alrami.saas.tuxis.net [31.3.111.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 13 Jul 2022 12:41:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tuxis.nl; s=mail; h=from:reply-to:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=21v3MjjtEv2A268urblRxgJlNty/J0ald7SMYNf8yOA=; b=ZSBlmd1Ds+F20vJgYTkACaYdpU35rcJPzq47urcirWBxe/oX/rY2ISQY+jRLsRtAyCF8NF9fmwjiB Yk7kDPB8QfXpc4d3hdWnik1APoU7LLfkmzMTsV1inxXNm4VXRH3DRf0DdvqBHlQACupIpVX78Ydn7H 29Ly1wF0reR8v3OTsgPI0hElRnCPVq4j+G8hwJaEfhmmR4v6DyV5bQ4fEDXobZtjuEDFtH74qdmMWD XpKhXKHAesVC3sX095T5duhAgIBvZkpzxQgSJboy35hJmyKKtoxjM/kWqP+lZ5QKU3/azWbRmqkymT 3t4CYPyD3UaxPgjm162CiXn4knlxhMA== X-Footer: dHV4aXMubmw= Received: from [IPv6:2a03:7900:64::1001] ([2a03:7900:64::1001]) (authenticated user mark@tuxis.nl) by kerio.tuxis.nl (Kerio Connect 9.4.1 patch 1) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Wed, 13 Jul 2022 12:41:13 +0200 From: "Mark Schouten" To: "Thomas Lamprecht" , "Proxmox Backup Server development discussion" Date: Wed, 13 Jul 2022 10:41:07 +0000 Message-Id: In-Reply-To: <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com> References: <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com> Reply-To: "Mark Schouten" User-Agent: eM_Client/9.0.1755.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.027 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] Scheduler causing connectivity issues? X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2022 10:41:50 -0000 Requested files sent offlist. =E2=80=94 Mark Schouten, CTO Tuxis B.V. mark@tuxis.nl ------ Original Message ------ >From "Thomas Lamprecht" To "Mark Schouten" ; "Proxmox Backup Server development=20 discussion" Date 13/07/2022 10:14:07 Subject Re: [pbs-devel] Scheduler causing connectivity issues? >Hi, > >Am 11/07/2022 um 10:44 schrieb Mark Schouten: >>>>Hope you guys can find something.. If I need to debug anything, let me= know! >>> >>>Thanks for the info, this already helps quite a bit. We'll look into it= and re-check >>>with you if we need more info. >>> >> >>Any chance you can think of a workaround for the time being, other than d= owngrading? > > >We identified a few places where blocking operations (e.g., the list snaps= hots API >endpoint) that may starve the network request accept loop in some realisti= c scenarios, >we'll move those out to their own separate thread to avoid such blockage. > >FWIW, it would be still interesting to see a few metrics/CLI outputs from= an affected >system to hopefully ensure that there's nothing additional to that problem= . > >- `head /proc/pressure/*` for some general info if the system is overloade= d >- `ls /var/lib/proxmox-backup/jobstates` just out of interest >- `ss -tlpn` to see if another (old) proxy process is still accepting >- `uptime` > > >