Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for load balancers #9326

Closed
cescoffier opened this issue Apr 5, 2020 · 3 comments
Closed

Add support for load balancers #9326

cescoffier opened this issue Apr 5, 2020 · 3 comments
Labels
area/grpc gRPC kind/enhancement New feature or request triage/out-of-date This issue/PR is no longer valid or relevant

Comments

@cescoffier
Copy link
Member

No description provided.

@michalszynkiewicz
Copy link
Member

a post on using load balancer in grpc-java that sheds some light on the usage: https://sultanov.dev/blog/grpc-client-side-load-balancing/

@cescoffier cescoffier transferred this issue from another repository May 15, 2020
@cescoffier cescoffier added the area/grpc gRPC label May 15, 2020
@emmanuelbernard emmanuelbernard mentioned this issue May 15, 2020
Closed
6 tasks
@geoand geoand added the kind/enhancement New feature or request label May 15, 2020
@nragon
Copy link
Contributor

nragon commented Dec 29, 2020 •
edited
Loading

Any updates on this @emmanuelbernard? (considering #9264 roadmap)
Food for thoughts:

  • Add a new option to grpc client called "servers" (A comma delimited list of servers where the service is exposed (ex.: :,:,...))
  • Add new option to grpc client called "loadBalancer" which will map to defaultLoadBalancingPolicy to NettyChannelBuilder (default pick_first).
  • Servers will be resolver on DnsNameResolverProvider loaded by grpc core
  • Custom load balancers can be loaded with custom services (io.grpc.LoadBalancerProvider) just like PickFirstLoadBalancerProvider

This was referenced Mar 19, 2021
Merged
Closed
@cescoffier
Copy link
Member Author

This has been fixed, and Stork integration is going to make it even more flexible than the initial scope.

@cescoffier cescoffier added the triage/out-of-date This issue/PR is no longer valid or relevant label Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/grpc gRPC kind/enhancement New feature or request triage/out-of-date This issue/PR is no longer valid or relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cescoffier @michalszynkiewicz @geoand @nragon