search

envoyproxy / xds-relay

Caching, aggregation, and relaying for xDS compliant clients and origin servers
Apache License 2.0
132 stars 29 forks source link

xds relay cache version not consistent with upstream #149

Closed jyotimahapatra closed 4 years ago

jyotimahapatra commented 4 years ago

While debugging xds relay, i observed that the cache of xds relay and upstream is bit different. You can notice that the cache versions don't match for the same eds response.

➜  xds-relay-private git:(rule) em exec --stdin --tty envoymanager-main-6f668fd9d8-29hg2 -n envoymanager-staging  --container envoymanager-service-gojson -- curl -s "0:6070/entry_dump?key=kitchensink_staging_eds" | grep 'address\|version'
  "version": "21094b630cea76c2b600ab56ad9d47768c549763",
            "address": {
                "address": "10.42.29.94",
➜  xds-relay-private git:(rule) em exec --stdin --tty xdsrelay-main-6bb98b5f77-t8q2q -n xdsrelay-staging  --container xdsrelay-service-gojson -- curl -s 0:6070/cache/v3-eds_kitchensink | grep 'address\|VersionInfo'
        "VersionInfo": "ef4961de1df475b15e5b5d5908ed73eb72c2ac77",
                          "address": {
                                "address": "10.42.29.94",
                          "address": {
                                "address": "10.0.132.123",
jyotimahapatra commented 4 years ago

This was due to a bug in the upstream control plane.