3 Commits (2274f35c89ceb6001542da5b94551981a51cd1f8)

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
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	f936ca5aea	grpc: client conn pool and resolver ... Extracted from 936522a13c Co-authored-by: Paul Banks <banks@banksco.de>	4 years ago