open-consul/agent/grpc-external/services/peerstream
Luke Kysow 17594a123e
peering: retry establishing connection more quickly on certain errors (#13938)
When we receive a FailedPrecondition error, retry that more quickly
because we expect it will resolve shortly. This is particularly
important in the context of Consul servers behind a load balancer
because when establishing a connection we have to retry until we
randomly land on a leader node.

The default retry backoff goes from 2s, 4s, 8s, etc. which can result in
very long delays quite quickly. Instead, this backoff retries in 8ms
five times, then goes exponentially from there: 16ms, 32ms, ... up to a
max of 8152ms.
2022-07-29 13:04:32 -07:00
..
health_snapshot.go Remove duplicate comment 2022-07-26 10:19:49 -07:00
health_snapshot_test.go
mock_ACLResolver.go
replication.go
server.go
stream_resources.go peering: retry establishing connection more quickly on certain errors (#13938) 2022-07-29 13:04:32 -07:00
stream_test.go peering: retry establishing connection more quickly on certain errors (#13938) 2022-07-29 13:04:32 -07:00
stream_tracker.go Rename receive to recv in tracker (#13896) 2022-07-25 16:08:03 -07:00
stream_tracker_test.go peering: read endpoints can now return failing status (#13849) 2022-07-25 14:27:53 -07:00
subscription_blocking.go
subscription_manager.go
subscription_manager_test.go
subscription_state.go
subscription_state_test.go
subscription_view.go
subscription_view_test.go
testing.go