Adjusting cluster invoker checks
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
The current check on cluster invoker is placed in the corresponding implementation class, and almost all implementation classes of AbstractClusterInvoker will call this method.
for example:

However, when the cluster invokers are empty, the subsequent load balancing process is useless.

So I think the check for clustered invokers should be adjusted。

Contributor guide
Research direction
Start by locating AbstractClusterInvoker and the implementation classes that call its cluster-invoker check. Compare the current check with the subsequent load-balancing path shown in the issue. Done means empty cluster invokers are detected before unnecessary load balancing, with the surrounding behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100