11 Commits (bae0ccbe7f9175d95c4c9a1fadad65ee0178ff7e)

Author	SHA1	Message	Date
R.B. Boyer	e20e6348dd	areas: make the gRPC server tracker network area aware (#11748) ... Fixes a bug whereby servers present in multiple network areas would be properly segmented in the Router, but not in the gRPC mirror. This would lead servers in the current datacenter leaving from a network area (possibly during the network area's removal) from deleting their own records that still exist in the standard WAN area. The gRPC client stack uses the gRPC server tracker to execute all RPCs, even those targeting members of the current datacenter (which is unlike the net/rpc stack which has a bypass mechanism). This would manifest as a gRPC method call never opening a socket because it would block forever waiting for the current datacenter's pool of servers to be non-empty.	3 years ago
R.B. Boyer	5b6d96d27d	grpc: ensure that streaming gRPC requests work over mesh gateway based wan federation (#10838) ... Fixes #10796	3 years ago
R.B. Boyer	fc9b1a277d	sync changes to oss files made in enterprise (#10670)	3 years ago
Daniel Nephin	29e93f6338	grpc: fix a data race by using a static resolver ... We have seen test flakes caused by 'concurrent map read and map write', and the race detector reports the problem as well (prevent us from running some tests with -race). The root of the problem is the grpc expects resolvers to be registered at init time before any requests are made, but we were using a separate resolver for each test. This commit introduces a resolver registry. The registry is registered as the single resolver for the consul scheme. Each test uses the Authority section of the target (instead of the scheme) to identify the resolver that should be used for the test. The scheme is used for lookup, which is why it can no longer be used as the unique key. This allows us to use a lock around the map of resolvers, preventing the data race.	4 years ago
Daniel Nephin	8bcd5040c7	agent/grpc: Add an integration test for ClientPool with TLS ... Also deregister the resolver.Builder in tests.	4 years ago
Daniel Nephin	d8299670cc	agent/grpc/resolver: namespace the server ID with the DC name ... So that if two datacenters end up with overlapping serverIDs we don't send requests to the wrong server	4 years ago
Daniel Nephin	e6ffd987a3	agent/grpc: seed the rand for shuffling servers	4 years ago
Daniel Nephin	2294793357	agent/grpc: use router.Manager to handle the rebalance ... The router.Manager is already rebalancing servers for other connection pools, so it can call into our resolver to do the same. This change allows us to remove the serf dependency from resolverBuilder, and remove Datacenter from the config. Also revert the change to refreshServerRebalanceTimer	4 years ago
Daniel Nephin	2273673500	grpc: restore integration tests for grpc client conn pool ... Add a fake rpc Listener	4 years ago
Daniel Nephin	bad4d3ff7c	grpc: redeuce dependencies, unexport, and add godoc ... Rename GRPCClient to ClientConnPool. This type appears to be more of a conn pool than a client. The clients receive the connections from this pool. Reduce some dependencies by adjusting the interface baoundaries. Remove the need to create a second slice of Servers, just to pick one and throw the rest away. Unexport serverResolver, it is not used outside the package. Use a RWMutex for ServerResolverBuilder, some locking is read-only. Add more godoc.	4 years ago
Daniel Nephin	25f47b46e1	grpc: move client conn pool to grpc package	4 years ago