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

L9 update: Remove internal link #444

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

L9 update: Remove internal link #444

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
be2ef2e
Cleanup
aranjans Jun 25, 2024
b76f818
Update L9-go-resolver-balancer-API.md
aranjans Jul 1, 2024
4f689b0
Update the lb config link
aranjans Jul 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion L9-go-resolver-balancer-API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ gRPC first gets an address picked by the balancer. Balancer picks the address ba

#### The balancing policy needs to be changed on service config updates

Upon service config updating, gRPC will look at the LoadBalancingPolicy field and decide which balancing policy to use. If the LoadBalancingPolicy specified by the service config is different from what's currently being used, gRPC should be able to change the policy. Refer to go/grpc-service-config for more details on this.
Upon service config updating, gRPC will look at the LoadBalancingPolicy field and decide which balancing policy to use. If the LoadBalancingPolicy specified by the service config is different from what's currently being used, gRPC should be able to change the policy. Refer to [master/A24-lb-policy-config.md](https://github.com/grpc/proposal/blob/master/A24-lb-policy-config.md) for more details on this.

Right now, there's no API to notify balancer of service config changes, so to change the balancing policy, the balancer needs to be swapped out. But swapping out the balancer and at the same time keeping the old resolver and address pool is not feasible because of the v1 structure.

Expand Down