[Feature] <title>指标采集数据量很大，导致存储数据到victoria-metrics，会导致http请求直接卡爆，没有资源可用

[zzmJava]

Feature Request

6.788 [warehouse-persistent-data-storage] ERROR org.apache.monitor.warehouse.store.history.vm.VictoriaMetricsClusterDataStorage Line:192 - flush metrics data to victoria-metrics error: I/O error on POST request for "http://192.168.65.70:8480/insert/0/prometheus/api/v1/import": Cannot assign requested address.
org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://192.168.65.70:8480/insert/0/prometheus/api/v1/import": Cannot assign requested address
at org.springframework.web.client.RestTemplate.createResourceAccessException(RestTemplate.java:915)

Is your feature request related to a problem? Please describe

No response

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[zqr10159]

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.