From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id D0E761FF14C for ; Fri, 29 May 2026 15:30:34 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 684DABCC4; Fri, 29 May 2026 15:30:31 +0200 (CEST) From: Dominik Csapak To: pdm-devel@lists.proxmox.com Subject: [PATCH datacenter-manager 0/4] implement back-off mechanism for Date: Fri, 29 May 2026 15:30:16 +0200 Message-ID: <20260529133026.3149896-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.049 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [mod.rs,connection.rs] Message-ID-Hash: TNHJLKIIMKYJ4AABNFJTYY5DCZFGVP73 X-Message-ID-Hash: TNHJLKIIMKYJ4AABNFJTYY5DCZFGVP73 X-MailFrom: d.csapak@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: 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 implments a basic back-off mechanism that increases the time between actual api calls in an exponential way (up to a maximum). Advantage are less failed api calls, but the downside is that it now takes a while potentially to mark a remote as reachable again. For details on ideas for that see the notes in patch 2/4 Note: patch 1/4 is related, but it's a fix on its own (see the notes there for further details.) Dominik Csapak (4): server: connection: multi client: use correct client error for retrying server: remote cache: prepare for back-off mechanism server: connection: multi-client: use back-off state from remote cache server: pbs client: rework to use the back-off mechanism from remote cache server/src/connection.rs | 42 +++++++-- server/src/pbs_client.rs | 167 +++++++++++++++++++++++++-------- server/src/remote_cache/mod.rs | 139 +++++++++++++++++++++++++++ 3 files changed, 300 insertions(+), 48 deletions(-) -- 2.47.3