Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstream: Introducing close_connections_on_host_set_change property #7675
upstream: Introducing close_connections_on_host_set_change property #7675
Changes from 16 commits
ba2f255
92ad8d5
888640c
77cf3c6
853343b
b336b6b
36d0ee4
d351954
09b185a
42cfdb2
213ed5a
ad3ba43
92019f1
6900e8a
88abfa4
5c4129c
ba07c8e
22f49f4
f4a1a4a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed this on my last pass: this callback only triggers when hosts are added or removed. For example, a change to host weights would not trigger this callback, instead only triggering callbacks added with
addPriorityUpdateCb
for the appropriate priority. Not sure if this is intended or not, just pointing it out.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any way to have some common code for this test and the previous test since I'm guessing they are mostly the same? Also I wonder if the not draining case is already well covered but I'm fine either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattklein123 don't think is worth the effort to introduce common code/method to share between two tests, since that code would be very specific to those 2 tests. Think is nice to still have 2 tests, to test when property is set vs not set. Could try to reduce the code size of second test (basically we want to ensure that connections are not drained on host addition). WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies, i have to do force push to fix DCO (DCO broke after committing suggestions). Reduced test size in last commit, waiting for opinions.