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

A17: Client-Side Health Checking #97

Merged
merged 7 commits into from
Oct 9, 2018
Merged

A17: Client-Side Health Checking #97

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
8b40b2b
A17: Client-Side Health Checking
markdroth Aug 27, 2018
dba553b
Add link to discussion thread.
markdroth Aug 27, 2018
b5e2727
review changes
markdroth Aug 27, 2018
0c64084
Fix backwardsness.
markdroth Aug 27, 2018
d459791
Change service config to use google.protobuf.StringValue instead of s…
markdroth Aug 27, 2018
dbd6520
Addressed review comments from @a11r.
markdroth Sep 27, 2018
f435179
Added link to service config doc and example in JSON form.
markdroth Oct 1, 2018
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
Prev Previous commit
Next Next commit
Fix backwardsness.
  • Loading branch information
@markdroth
markdroth committed Aug 27, 2018
commit 0c640848e3f1227c3eacd78c1bfc27a6841732ea
2 changes: 1 addition & 1 deletion A17-client-side-health-checking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ When a client receives a health-checking response from the backend,
if the health check response indicates that the backend is healthy, the
subchannel will transition to state READY; otherwise, it will transition
to state `TRANSIENT_FAILURE`. Note that this means that when a backend
transitions from healthy to unhealthy, the subchannel's connectivity state
transitions from unhealthy to healthy, the subchannel's connectivity state
will transition from `TRANSIENT_FAILURE` directly to `READY`, with no stop at
CONNECTING in between. This is a new transition that was not [previously
supported](https://github.com/grpc/grpc/blob/master/doc/connectivity-semantics-and-api.md), although it is unlikely to be a problem for applications,
Expand Down