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 080961FF13A for ; Wed, 27 May 2026 18:02:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6D8DCDF7; Wed, 27 May 2026 18:02:00 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH datacenter-manager] server: location cache: also update cache if a location was removed Date: Wed, 27 May 2026 18:01:48 +0200 Message-ID: <177989770777.476509.14963855732573194616.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260527152106.436183-1-s.sterz@proxmox.com> References: <20260527152106.436183-1-s.sterz@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: 1779897690256 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: RUESGGCL27HXTBX4HVRWAWGZ32GIOXB7 X-Message-ID-Hash: RUESGGCL27HXTBX4HVRWAWGZ32GIOXB7 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 Wed, 27 May 2026 17:21:06 +0200, Shannon Sterz wrote: > this removes all locations from the cache if the remote has no > location anymore. otherwise clients may be served inconsitent data > depending on how the max age property is set. showing no location when > max-age is provided with a low value, but the cached location if it > isn't. > > note that removing it would leave us in a race with newer writers as > the `set_if_newer_with_timestamp` has no equivalent for remove. so set > `None` in the cache instead for those cases. > > [...] Applied, thanks! [1/1] server: location cache: also update cache if a location was removed commit: 50b8abaecbcfebcfc68e39af3fba6c2b089e4d94