Skip to content

xds_protocol: make explicit that updates only occur when resources ch…#328

Merged
htuch merged 1 commit intoenvoyproxy:masterfrom
htuch:xds-loopy
Dec 7, 2017
Merged

xds_protocol: make explicit that updates only occur when resources ch…#328
htuch merged 1 commit intoenvoyproxy:masterfrom
htuch:xds-loopy

Conversation

@htuch
Copy link
Copy Markdown
Member

@htuch htuch commented Dec 6, 2017

…ange.

This comes up a fair bit in discussion with management server
implementers, @ramaraochavali suggested we explain this.

Signed-off-by: Harvey Tuch htuch@google.com

…ange.

This comes up a fair bit in discussion with management server
implementers, @ramaraochavali suggested we explain this.

Signed-off-by: Harvey Tuch <htuch@google.com>
@htuch
Copy link
Copy Markdown
Member Author

htuch commented Dec 6, 2017

Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth opening an issue around detecting spinning and/or rate-limiting the number of discovery requests that we send (with strong warning emitted), since I agree this is going to be a very common issue.

@htuch htuch merged commit 38c35f0 into envoyproxy:master Dec 7, 2017
@htuch htuch deleted the xds-loopy branch December 7, 2017 14:53
@htuch
Copy link
Copy Markdown
Member Author

htuch commented Dec 7, 2017

Issue filed at envoyproxy/envoy#2169.

Copy link
Copy Markdown
Contributor

@ramaraochavali ramaraochavali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants