From 46b8b8d08fa2b9c80908b4b2c38b8ddacbb993f8 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Tue, 21 Oct 2025 11:21:12 +0000 Subject: [PATCH] fix: increase pulse-sensor-proxy rate limits for multi-node support - Increase rate limit from 1 req/5sec to 1 req/sec (60/min) - Increase burst from 2 to 5 requests - Fixes temperature collection failures when monitoring 3+ nodes - All requests from containerized Pulse use same UID, causing rate limiting - New limits support 5-10 node deployments comfortably Resolves issue where adding standalone nodes broke temperature monitoring for all nodes due to aggressive rate limiting. --- cmd/pulse-sensor-proxy/throttle.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cmd/pulse-sensor-proxy/throttle.go b/cmd/pulse-sensor-proxy/throttle.go index 3d07b0618..59cc32728 100644 --- a/cmd/pulse-sensor-proxy/throttle.go +++ b/cmd/pulse-sensor-proxy/throttle.go @@ -38,13 +38,13 @@ type rateLimiter struct { } const ( - defaultPerPeerBurst = 2 + defaultPerPeerBurst = 5 // Allow burst of 5 requests for multi-node polling defaultPerPeerConcurrency = 2 defaultGlobalConcurrency = 8 ) var ( - defaultPerPeerRateInterval = 5 * time.Second // 0.2 qps (~12/min) + defaultPerPeerRateInterval = 1 * time.Second // 1 qps (60/min) - supports 5-10 node deployments defaultPenaltyDuration = 2 * time.Second defaultPerPeerLimit = rate.Every(defaultPerPeerRateInterval) )