diff options
| author |  Juanli Shen <aspirinsjl@gmail.com> | 2017-09-13 15:10:08 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2017-09-13 15:10:08 -0700 |
| commit | 324ad6a6c239ebb6dfafbe00a825a90a409daa11 (patch) | |
| tree | 34f3a57ef2ce083b0044d64f314006588e478562 /doc/service_config.md | |
| parent | fc57518ac1999743da3f618193e9d2240a5660c1 (diff) | |
Update service_config doc
The current grpclb fallback implementation is to continue using the internal round_robin policy but feed it with the backends from the resolver. We didn't fall back to the policy indicated in service config (or client API) because that's too complex and has more different behavior from the normal situation where we do connect to the balancer.
Diffstat (limited to 'doc/service_config.md')
| -rw-r--r-- | doc/service_config.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/doc/service_config.md b/doc/service_config.md index 99d985f3bf..0abbd7f324 100644 --- a/doc/service_config.md +++ b/doc/service_config.md @@ -24,10 +24,7 @@ The service config is a JSON string of the following form: // opposed to backend addresses), gRPC will use grpclb (see // https://github.com/grpc/grpc/blob/master/doc/load-balancing.md), // regardless of what LB policy is requested either here or via the - // client API. However, if the resolver returns at least one backend - // address in addition to the balancer address(es), the client may fall - // back to the requested policy if it is unable to reach any of the - // grpclb load balancers. + // client API. 'loadBalancingPolicy': string, // Per-method configuration. Optional. |