GLGGAG opened a new issue, #15762: URL: https://github.com/apache/dubbo/issues/15762
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo java 3.3.0 OpenJdk 1.8 ### Steps to reproduce this issue We encountered an issue with the RoundRobinLoadBalance algorithm in Dubbo 3.3.x. Every day at around 06:00, our service scales out quickly from ~50 pods to ~200 pods (Kubernetes HPA). During this period, we observed that some newly started pods receive significantly more traffic than the original pods, instead of being gradually warmed up and balanced evenly. The traffic spike pattern looks like this (per-instance QPS monitoring): (Monitoring screenshot: newly added pods show much higher QPS than older ones) <img width="3906" height="728" alt="Image" src="https://github.com/user-attachments/assets/bb3e78ba-6ee1-4ee9-961b-e64332174d59"; /> ### What you expected to happen Expected behavior: New providers should receive traffic smoothly and proportional to weight/warm‑up rules The load should not skew heavily to newly added pods immediately after scaling Actual behavior: Newly started pods receive higher QPS compared to existing pods for roughly 1–5 minutes after scaling This causes CPU / thread pool spikes and temporary service instability on those pods ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
