adgarr

> -http.idleConnTimeout duration > Timeout for incoming idle http connections (default 1m0s) vminsert and vmselect are using the same loadbalancer. And idleConnTimeout is set to 5m in loadbalancer.\ The error...

> Hello @adgarr Based on the graphs you've provided it looks like there is a [spike in churn rate](https://docs.victoriametrics.com/faq/#what-is-high-churn-rate) around 09:30. Spike in churn rate requires a TSDB to register...

@zekker6 The storage node is not running any other applications. I will modify the configuration a bit and update the version, then check the results. Thank you again!

@zekker6 I updated the application from version 93 to version 103 in the testing environment around 3 PM and found that the performance seems to have worsened. The number of...

@zekker6 Hello, I updated the environment from version 93 to version 103 in the production environment last night, removed the cache configuration for the storage nodes, and updated the monitoring...

@zekker6 The storage nodes have not been restarted, but multiple storage nodes have been rerouted. I guess it might be due to the high CPU usage of these storage nodes,...

@zekker6 Today, I encountered this type of issue where the CPU usage on this node spiked, and it rerouted to other nodes. The storage service on this node is functioning...

@zekker6 What causes a particular node to suddenly overload? I prefer not to disable reroute. Each storage node holds 8TB of data; could it be that querying this node requires...