zqr10159 commented on issue #4079: URL: https://github.com/apache/hertzbeat/issues/4079#issuecomment-4094674137
From the error message, this looks more like a **client-side write path issue in HertzBeat** than a VictoriaMetrics server bug. `Cannot assign requested address` usually means the HTTP client ran out of local socket / ephemeral port resources while sending requests, rather than VictoriaMetrics returning an explicit server-side error. In HertzBeat, the VictoriaMetrics path uses **`RestTemplate` + HTTP import + local buffer/flush logic**. Under high metric volume, this can easily amplify pressure on the client side. For large-scale metric ingestion, I would recommend using **GreptimeDB** instead. In HertzBeat, Greptime writes go through the **Greptime Java client / gRPC**, not the same HTTP import path, so connection management is more stable and it is much less likely to hit this kind of local resource exhaustion problem. So if the workload is large, switching to **GreptimeDB** should be a more reliable option. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@hertzbeat.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@hertzbeat.apache.org For additional commands, e-mail: notifications-h...@hertzbeat.apache.org
