You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When onCancel is called from go-control-plane to the Orchestrator, Orchestrator removes management of this watch, but the watch persists in the Cache until the TTL expires. We could more effectively manage resources if a DeleteWatch(req *v2.DiscoveryRequest) function existed.
The text was updated successfully, but these errors were encountered:
Fixes#57
This change adds an API to the cache to support deleting a request when given the key and the (pointer to the) request, which the orchestrator can use upon cancellation. If the key is not in the cache, nothing happens.
The input type to AddRequest was also changed to take a pointer to a request.
Signed-off-by: Lisa Lu <lisalu@lyft.com>
jessicayuen
pushed a commit
to jessicayuen/xds-relay
that referenced
this issue
Apr 24, 2020
Fixesenvoyproxy#57
This change adds an API to the cache to support deleting a request when given the key and the (pointer to the) request, which the orchestrator can use upon cancellation. If the key is not in the cache, nothing happens.
The input type to AddRequest was also changed to take a pointer to a request.
Signed-off-by: Lisa Lu <lisalu@lyft.com>
When onCancel is called from go-control-plane to the Orchestrator, Orchestrator removes management of this watch, but the watch persists in the Cache until the TTL expires. We could more effectively manage resources if a DeleteWatch(req *v2.DiscoveryRequest) function existed.
The text was updated successfully, but these errors were encountered: