[GH-ISSUE #4435] [Feature Request] Can load balancing support more strategies like weighted round robin?

gitea-mirror commented

2026-05-05 14:15:01 -06:00

Owner

Copy link

Originally created by @rty813 on GitHub (Sep 13, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4435

Describe the feature request

Currently, the load balancing strategy only supports round-robin. Is there any consideration to add more strategies?

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @rty813 on GitHub (Sep 13, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4435 ### Describe the feature request Currently, the load balancing strategy only supports round-robin. Is there any consideration to add more strategies? ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:15:01 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:15:05 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Sep 13, 2024):

This is a low-priority long-term plan that will not be realized in the short term.

@fatedier commented on GitHub (Sep 13, 2024): This is a low-priority long-term plan that will not be realized in the short term.

gitea-mirror commented

2026-05-05 14:15:05 -06:00

Author

Owner

Copy link

@rty813 commented on GitHub (Sep 14, 2024):

Looking forward to this feature

@rty813 commented on GitHub (Sep 14, 2024): Looking forward to this feature

gitea-mirror commented

2026-05-05 14:15:06 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 6, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Oct 6, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified