Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Grpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tci-gateway-module
Grpc
Commits
e860359f
Commit
e860359f
authored
8 years ago
by
Mark D. Roth
Browse files
Options
Downloads
Patches
Plain Diff
Attempt to fix formatting.
parent
b4227370
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/load-balancing.md
+3
-3
3 additions, 3 deletions
doc/load-balancing.md
with
3 additions
and
3 deletions
doc/load-balancing.md
+
3
−
3
View file @
e860359f
...
@@ -125,7 +125,7 @@ works:
...
@@ -125,7 +125,7 @@ works:
address returned by the resolver. Note that these policies
address returned by the resolver. Note that these policies
ignore any balancer addresses returned by the resolver.
ignore any balancer addresses returned by the resolver.
-
In the case of the
`grpclb`
policy, the workflow is as follows:
-
In the case of the
`grpclb`
policy, the workflow is as follows:
a
. The policy opens a stream to one of the balancer addresses returned
1
.
The policy opens a stream to one of the balancer addresses returned
by the resolver. It asks the balancer for the server addresses to
by the resolver. It asks the balancer for the server addresses to
use for the server name originally requested by the client (i.e.,
use for the server name originally requested by the client (i.e.,
the same one originally passed to the name resolver).
the same one originally passed to the name resolver).
...
@@ -133,10 +133,10 @@ works:
...
@@ -133,10 +133,10 @@ works:
addresses returned by the resolver. However, in the future, it
addresses returned by the resolver. However, in the future, it
may be changed to use these addresses as a fallback in case no
may be changed to use these addresses as a fallback in case no
balancers can be contacted.
balancers can be contacted.
b
. The gRPC servers to which the load balancer is directing the client
2
.
The gRPC servers to which the load balancer is directing the client
may report load to the load balancers, if that information is needed
may report load to the load balancers, if that information is needed
by the load balancer's configuration.
by the load balancer's configuration.
c
. The load balancer returns a server list to the gRPC client's
`grpclb`
3
.
The load balancer returns a server list to the gRPC client's
`grpclb`
policy. The
`grpclb`
policy will then create a subchannel to each of
policy. The
`grpclb`
policy will then create a subchannel to each of
server in the list.
server in the list.
4.
For each RPC sent, the load balancing policy decides which
4.
For each RPC sent, the load balancing policy decides which
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment