From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id AA3401FF153 for ; Mon, 22 Jun 2026 20:16:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E0734122E2; Mon, 22 Jun 2026 20:16:43 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH datacenter-manager v2 0/4] implement back-off mechanism for connection errors for remotes Date: Mon, 22 Jun 2026 20:13:27 +0200 Message-ID: <178215200489.2888775.18421259188232230100.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260608132539.2949407-1-d.csapak@proxmox.com> References: <20260608132539.2949407-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782152158873 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: XZZKX4OUZUYEGWAKQI35CLQBCN34XFU6 X-Message-ID-Hash: XZZKX4OUZUYEGWAKQI35CLQBCN34XFU6 X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 08 Jun 2026 15:25:28 +0200, Dominik Csapak wrote: > When a remote is not reachable (e.g. network outage, crashes, etc), PDM > tries to connect on every attempt with a timeout. This leads to heavily > delayed api calls in the PDM UI. To counter that, this series implements > a basic back-off mechanism that increases the time between actual api > calls in an exponential way (up to a maximum). > > For details on how the back-off mechanism works see patch 1/4 > > [...] Would have welcomed some more feedback from others, but given that this is basically just internal with no config, state file nor API exposure, it bascially can only improve the status quo, and if there are other ideas in the future we can still rework this relatively freely. Applied, thanks! [1/4] server: remote cache: prepare for back-off mechanism commit: 8f70828f8d88105dbe2c9b11a7b3731e9342414b [2/4] server: remote cache: introduce canary remote when none is reachable commit: bc68a91d9a1d1ac3a9fecadcd0cfce17cccb7bbe [3/4] server: connection: multi-client: use back-off state from remote cache commit: 41d60dd863d398dcd69b6993b1903eff55eb459d [4/4] tasks: remote node mapping: use host cache for PBS too commit: e380d2ddd6b3ea0fd0b3c732b1f668536aed297c