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
bc435e7e
Commit
bc435e7e
authored
9 years ago
by
yang-g
Browse files
Options
Downloads
Patches
Plain Diff
recommend to require empty service name
parent
481b016e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/health-checking.md
+6
-5
6 additions, 5 deletions
doc/health-checking.md
with
6 additions
and
5 deletions
doc/health-checking.md
+
6
−
5
View file @
bc435e7e
...
...
@@ -58,11 +58,12 @@ a response must be sent back with an `OK` status and the status field should be
set to
`SERVING`
or
`NOT_SERVING`
accordingly. If the service name is not
registered, the server returns a
`NOT_FOUND`
GRPC status.
It is recommended that the server use an empty string as the key for server’s
health status as a whole. The server can just do exact matching of the
service name support any kind of wildcard matching. However, the service owner
has the freedom to implement more complicated matching semantics that both the
client and server agree upon.
The server should use an empty string as the key for server’s
overall health status, so that a client not interested in a specific service can
query the server's status with an empty request. The server can just do exact
matching of the service name without support of any kind of wildcard matching.
However, the service owner has the freedom to implement more complicated
matching semantics that both the client and server agree upon.
A client can declare the server as unhealthy if the rpc is not finished after
some amount of time. The client should be able to handle the case where server
...
...
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