为什么负载均衡负责使用ShortestResponseLoadBalance就避免了LeastActiveLoadBalance的缺点了呢？
Open
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
LeastActiveLoadBalance缺点是如果有一台性能非常差的服务器，则性能最好的服务器将会到达极限，
https://github.com/apache/dubbo/pull/6064
那为什么使用ShortestResponseLoadBalance最短时间就解决这个问题了呢？
最短时间不也是类似于LeastActiveLoadBalance比较数字大小这类算法嘛，
内部是什么原理呢？感谢
@Augustvic
Contributor guide
Research direction
Read PR 6064 and compare the LeastActiveLoadBalance and ShortestResponseLoadBalance implementations in Apache Dubbo. Trace how each metric is obtained and used during selection, then document why the shortest-response approach addresses the described slow-server scenario, with tests or examples showing the distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100