grpc-go

Commit Graph

Author	SHA1	Message	Date
Doug Fawley	c91396d4e1	pickfirst: do not return initial subconn while connecting (#5825 ) Fixes https://github.com/grpc/grpc-go/issues/5293	2022-11-30 08:57:17 -08:00
Doug Fawley	9f97673ba4	test: move e2e goaway tests to goaway_test.go (#5820 )	2022-11-29 10:08:03 -08:00
赵延	c44f627fd1	cleanup: replace grpc.WithInsecure with insecure.NewCredentials (#5177 )	2022-02-09 11:17:46 -08:00
Doug Fawley	0d6a24f68a	test: move stubServer to separate package in internal (#4081 )	2020-12-04 15:56:07 -08:00
Doug Fawley	02cd07d9bb	cmd/protoc-gen-go-grpc: revert to interface-based service registration (#3911 )	2020-09-29 15:17:06 -07:00
Doug Fawley	ff9dd65c90	protoc-gen-go-grpc: generate interfaces optionally; remove NewFooService (#3876 )	2020-09-16 10:15:56 -07:00
Doug Fawley	44d73dff99	cmd/protoc-gen-go-grpc: rework service registration (#3828 )	2020-08-25 09:28:01 -07:00
Doug Fawley	977142214c	client: fix race between transport draining and new RPCs (#2919 ) Before these fixes, it was possible to see errors on new RPCs after a connection began draining, and before establishing a new connection. There is an inherent race between choosing a SubConn and attempting to creating a stream on it. We should be able to avoid application-visible RPC errors due to this with transparent retry. However, several bugs were preventing this from working correctly: 1. Non-wait-for-ready RPCs were skipping transparent retry, though the retry design calls for retrying them. 2. The transport closed itself (and would consequently error new RPCs) before notifying the SubConn that it was draining. 3. The SubConn wasn't synchronously updating itself once it was notified about the closing or draining state. 4. The SubConn would go into the TRANSIENT_FAILURE state instantaneously, causing RPCs to fail instead of queue.	2019-07-22 16:07:55 -07:00

8 Commits