Jess Yuen

Update statsd reporting README instructions

3

* Fix invalid variable reference, s/r/reporter * Remove references to [legacy statsd client](https://github.com/cactus/go-statsd-client/blob/v3.2.0/statsd/client_legacy.go#L32)

WIP/POC. * Add concept of upstream gRPC stream Send / Recv timeouts. * Send timeouts (from the proto): ``` // Optional. Maximum timeout for blocked gRPC sends. // If this...

Signed-off-by: Jess Yuen

Unable to run these unit tests in a jailed/network-less environment: ``` 14:26:06 FAIL github.com/envoyproxy/xds-relay/internal/app/cache [setup failed] 14:26:06 # github.com/envoyproxy/xds-relay/internal/app/mapper 14:26:06 package github.com/envoyproxy/xds-relay/internal/app/mapper (test) 14:26:06 imports github.com/onsi/ginkgo: github.com/onsi/[email protected]: Get "/github.com/onsi/ginkgo/@v/v1.12.0.zip": dial...

Implement retries on stream open failures from orchestrator -> origin server

8

Currently, we just error out. Implement configurable retry and back-off logic to re-attempt to open the stream on failures. Currently we force close all downstream connections, forcing downstream clients to...

Support the freeform 'metadata' field in the aggregation rules. API: https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/base.proto

Flaky behavior in unit test

1

``` --- FAIL: TestGoldenPath (0.00s) panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation...

There is a potential race condition between the delete operation and the two operations (get response channel, add response) here: https://github.com/envoyproxy/xds-relay/blob/37af3c5c5e65772d6bb5b0841ca117ff09c99c60/internal/app/orchestrator/orchestrator.go#L340-L341

Cache is in the format `aggregated_key: {Response, Requests[]}` `Request` is a pointer to the entire request object, which means that subsequent (N)ACKs (which increments the nonce) are mutating the cache....

See: https://github.com/envoyproxy/xds-relay/pull/53/files#diff-2958638164db92742469d2bb08d0001aR122-R128 There are possibilities that a discovery request won't get correctly bucketed into a aggregation rule defined on server bootstrap. Rather than dropping this request, we'd like to continue...