Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #23642 from techieshark/patch-1

Browse Source 
Clarify meaning of 'lameduck'
pull/24095/head
Mark D. Roth 4 years ago committed by GitHub
parent ac5cca327a 653ba624cf
commit 791fb0bbcb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      doc/PROTOCOL-HTTP2.md

2
doc/PROTOCOL-HTTP2.md
Unescape View File

@ -215,7 +215,7 @@ The following mapping from RST_STREAM error codes to GRPC error codes is applied
HTTP2 Code|GRPC Code HTTP2 Code|GRPC Code
----------|----------- ----------|-----------
NO_ERROR(0)|INTERNAL - An explicit GRPC status of OK should have been sent but this might be used to aggressively lameduck in some scenarios. NO_ERROR(0)|INTERNAL - An explicit GRPC status of OK should have been sent but this might be used to aggressively [lameduck](https://landing.google.com/sre/sre-book/chapters/load-balancing-datacenter/#identifying-bad-tasks-flow-control-and-lame-ducks-bEs0uy) in some scenarios.
PROTOCOL_ERROR(1)|INTERNAL PROTOCOL_ERROR(1)|INTERNAL
INTERNAL_ERROR(2)|INTERNAL INTERNAL_ERROR(2)|INTERNAL
FLOW_CONTROL_ERROR(3)|INTERNAL FLOW_CONTROL_ERROR(3)|INTERNAL

Write Preview
Loading…
Cancel
Save